Pressing the CONTINUE button will create the MOP entity on the node you
    are managing.

    A NET$MOP process must already be present on the system before you can
    successfully create the MOP entity.  If a NET$MOP process does not
    exist, you can start MOP using the following command:

    $ @SYS$SYSTEM:STARTUP NETWORK MOP

    The NET$STARTUP_MOP system logical should be defined in
    SYS$MANAGER:NET$LOGICALS.COM if you want to automatically start up MOP
    when the system reboots.  See the SYS$MANAGER:NET$LOGICALS.TEMPLATE
    file if your SYS$MANAGER:NET$LOGICALS.COM file does not already exist.

    Pressing the CANCEL button will dismiss the window with no action taken.

1  –  Circuit

    Creates a MOP Circuit entity that represents a data link circuit on
    which MOP services are available.  Both the Circuit Name and the
    Circuit Type are required arguments.  An example of a Circuit Name
    is CSMACD-0.  An example of a Circuit Type is CSMA-CD.

    Press the CONTINUE button to create the MOP Circuit entity, or press
    the CANCEL button to cancel this operation.  In either case, you will
    return to the main window.

2  –  Client

    Creates a MOP Client entity.  A MOP Client entity is a set of default
    characteristics used by the MOP functions Dump Server, Load Server, Load
    Requester, Loop Requester and Console Requester.  When a command or
    request for one of these services does not supply all of the required
    arguments, the values stored by in the Client entity are used to
    perform the operation.

    The Client Name argument is a required argument.

    Press the CONTINUE button to create the MOP Client entity with its
    default values, or press the CANCEL button to cancel this operation.
    In either case, you will return to the main window.