Creates the MOP module.  For information about this entity and
    its subentities, refer to HELP ENTITY MOP.  For information about
    managing MOP, refer to HELP NETWORK_MANAGEMENT MOP.

    create  [node node-id] mop

    Select circuit for information on creating mop circuit subentities.

    Select client for information on creating mop client subentities.

1  –  Exception Messages

 o  already exists

    A MOP module already exists.

 o  entity class not supported (OpenVMS)

    MOP has not registered with EMAA.  The NET$MOP process has probably
    not been properly started.  See HELP NETWORK_MANAGEMENT MOP for
    further information.

2  –  circuit

    Creates an instance of a mop circuit entity, identified by the
    circuit-name simplename.  This mop circuit entity is a data link on
    which MOP services are available.  The required Type attribute
    specifies the type of circuit.

    create  [node node-id] mop circuit circuit-name type circ-type

    Example:

    create mop circuit csmacd-1 type csma-cd

2.1  –  Exception Messages

 o  entity class not supported (OpenVMS)

    MOP has not registered with EMAA.  The NET$MOP process has
    probably not been properly started.  For more information,
    see HELP NETWORK_MANAGEMENT MOP.

 o  unsupported circuit type

    Type argument value is not supported in this implementation.

 o  already exists

    A mop circuit by this name already exists.

3  –  client

    Creates an instance of a mop client entity, identified by the
    client-name simplename.  A mop client is a set of default
    characteristics saved in the MOP Client database.

    create  [node node-id] mop client client-name

    These default characteristics are used by several MOP functions:
    dump/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 in the MOP client database for that client are
    used to perform the operation.

    Example:

    create mop client lamchp

3.1  –  Exception Messages

 o  entity class not supported (OpenVMS)

    The MOP entity has not registered with EMAA.  The NET$MOP
    process has probably not been started.  For more information,
    see HELP NETWORK_MANAGEMENT MOP.

 o  already exists

    The a mop client by that instance name already exists.

 o  no such object instance

    MOP has not been properly started or configured.