Phase V remote nodes are managed using NCL, and Phase IV remote
    nodes are managed using NCP.  Refer to the appropriate remote node
    type below for more information.

    For information on managing the remote console subsystem (ASCII
    console) of a network server on a LAN, refer to HELP
    NETWORK_MANAGEMENT TOOLS CONSOLE_CARRIER.

1  –  Phase V Nodes

    To issue NCL commands to remote Phase V nodes, simply include
    the remote nodename or address in the ncl command.  Normally,
    any access beyond an ncl "show" will require that some type of
    access control information is provided.  For information about how
    access control is handled on a remote node, refer to HELP
    NETWORK_MANAGEMENT ACCESS_CONTROL.

    To perform a series of ncl commands on a remote Phase V node, you
    may find it convenient to set up default entity and access control
    information within ncl using SET NCL DEFAULT commands.  For
    information on how to modify this default NCL context, refer to
    HELP NCL DEFAULT_CONTEXT.

    To specify access control information to be used for a single NCL
    command on the remote Phase V node, use either the "by" preposition
    or an access control string.  See HELP NCL SPECIFYING_ACCESS_CONTROL
    for more information.

2  –  Phase IV Nodes

    DECnet-Plus lets you manage remote systems running Phase IV software
    from a system running DECnet-Plus network management. To execute an
    NCP command, follow the specific platform instructions.

    Because NCL is not backwards compatible with NCP, NCP scripts do not
    work under the NCL utility. To run NCP scripts, you need to use the
    convert command in the decnet_migrate utility.  For more
    information on this utility, see the DECnet-Plus Network Management
    book or HELP NETWORK_MANAGEMENT TOOLS DECNET_MIGRATE.

2.1  –  Tru64 UNIX

    To manage remote Phase IV nodes on Tru64 UNIX, access NCP within
    the NCL utility, as in:

    ncl> ncp tell foobar show executor characteristics

    You must enter the entire NCP command at the ncl> prompt or type
    ncl ncp at the system prompt.  For example:

    %ncl ncp tell foobar show executor characteristics

2.2  –  OpenVMS

    You can use the NCP Emulator tool to manage remote Phase IV nodes
    with the TELL and SET EXECUTOR NODE commands.  The TELL command
    allows you to perform a single NCP command on the remote node, and
    you may choose to supply access control information within the
    command.  For example, to zero the executor counters on a remote
    Phase IV node from a local Phase V node, enter the following:

    $ run sys$system:ncp
    NCP> tell remnod"account password" zero exec counters

    The NCP Emulator tool is not intended for management of Phase V
    nodes, so all NCP commands are not supported.  The following
    error is returned if an unsupported NCP Emulator command is
    attempted on a Phase V system without specifying a remote
    Phase IV system:

    NCP> zero exec counters
    %NCP-W-SYSMGT, System-specific management function not supported

    When you wish to perform a series of commands on a single remote
    Phase IV node, you can set your default NCP context to that node
    using the NCP SET EXECUTOR NODE command; again you may choose to
    supply default access control information within that command.
    For example, after the following command is issued, all subsequent
    commands within that NCP session will be performed on node
    FAZ4ND using the specified access control information:

    $ mcr ncp
    NCP> set executor node faz4nd"account password"

    See HELP NETWORK_MANAGEMENT TOOLS NCP_EMULATOR for more
    information on the use of the NCP Emulator.