1  –  node (OpenVMS)

    The Phase IV NCP CONNECT NODE command has no Phase V equivalent.
    Instead, use the following command to access the console carrier
    function of MOP on Phase V:

    $SET HOST/MOP

    For further information about the Console Carrier, refer to
    the DECnet-Plus Network Management book, Appendix I.

2  –  via (OpenVMS)

    The Phase IV NCP CONNECT VIA command has no Phase V equivalent.
    Instead, use the following command to access the console carrier
    function of MOP on Phase V:

    $SET HOST/MOP

    For further information about the Console Carrier, refer to
    the DECnet-Plus Network Management book, Appendix I.

3  –  event_dispatcher

    Causes the outbound stream entity to request a connection to its
    sink partner. This directive causes the entity to issue a single
    session connect request to its sink partner, unless the state is
    already OnConnected, in which case the directive has no effect
    and returns the success response.

    connect  [node node-id] event dispatcher -
         outbound stream simple-name

3.1  –  Exception Messages

 o  connection failed

    The connection attempt failed. The exception may include
    additional arguments that give more information about the
    failure.

    Arguments:

    reason      The connection failed at the Session Control layer.

    data        This field can include optional data that describes
                the reason the connection attempt failed.

 o  no sink specified

    All of the sink specifier attributes are null.

 o  wrong state

    The operation failed because the entity was not in off,
    onconnecting, or ondisconnecting state.

 o  entity class not supported (OpenVMS)

    The Event Dispatcher is not registered with EMAA.  The NET$EVD
    process is probably not started.  For instructions on how to
    restart the Event Dispatcher, refer to HELP NETWORK_MANAGEMENT
    EVENT_DISPATCHER.