With the MOP (Maintenance Operations Protocol) module, you can:

    -  Downline load and upline dump
    -  Use the console carrier on a network server
    -  Use the configuration monitor
    -  Run lookback tests

    To set up a basic MOP configuration, invoke the configuration
    procedure:

    $ @sys$manager:net$configure

    Then select Option 1 "Perform an entire configuration", and
    answer YES to the Load MOP question to create new MOP client
    and circuit scripts.  Then select Option 8 "Configure MOP
    Client database" as many times as necessary to ADD or DELETE
    MOP Clients.

    Once MOP has been correctly configured, net$configure will
    have created net$mop_client_startup.ncl and
    net$mop_circuit_startup.ncl scripts.  The client script must
    contain, in addition to any default client information,
    CREATE MOP and ENABLE MOP commands.

    You may then add or delete MOP Clients at any time by
    invoking net$configure and selecting Option 8 "Configure MOP
    Client database" option.

    Anytime after MOP has been configured, you may control
    whether or not MOP starts automatically at boot time by
    defining (or not defining) the following system logical:

    $ define/system/nolog net$startup_mop true

    You will find this and other logicals (including some which
    affect MOP performance) in the net$logicals.com procedure.
    (Refer to HELP NETWORK_MANAGEMENT LOGICAL_NAMES for
    additional information on the net$logicals.com procedure.)

    Anytime after MOP has been configured, if no NET$MOP process
    is present, you may re-start it manually by:

    $ @sys$system:startup network mop

    For additional information on the configuration and use of MOP,
    refer to the DECnet-Plus Network Management book.