The COPY KNOWN NODES command updates the node database on the local
node.  You can copy the volatile or permanent database from a remote
node to either or both the volatile and permanent databases on the
local node.  You also have the option of clearing or purging the node
database on the local node before the copy operation is performed.

Only the node name and address are copied.  A node entry will not be
copied into the node database if it would result in the association
of two names with one address of two addresses with one name.


        COPY    KNOWN NODES     FROM node-id    USING
                                                TO
                                                WITH


All underscores found in parameters must be replaced with spaces
when parameters are used in NCP commands.

Additional information available:

KNOWN NODES

FROM node-idUSING optionTO optionWITH option
Examples

KNOWN NODES indicates that all nodes defined on the remote node are to
be copied (with the exception of loop nodes) to the local node.

Specifies the remote node from which the copy is to be made.

Specifies the node database on the remote node from which the infor-
mation is to be copied.  The two possible options are

        VOLATILE        Indicates that the volatile database on the
                        remote node is to be copied

        PERMANENT       Indicates that the permanent database on the
                        remote node is to be copied.

        The default is VOLATILE.

Specifies the node database on the local node to which the information
is to be copied.  The three possible options are

        VOLATILE        Indicates that the information is to be copied
                        to the volatile database on the local node.

        PERMANENT       Indicates that the information is to be copied
                        to the permanent database on the local node.

        BOTH            Indicates that the information is to be copied
                        to both the volatile and permanent databases
                        on the local node.

        The default is VOLATILE.

Clears or purges the node database on the local node before the copy
operation is performed.  Retains the executor node characteristics
and the name and address of the remote node from which the node infor-
mation is to be copied.  The node database to be cleared or purged is
the local database to which the information will be copied.  The two
options are listed below (note that you can actually specified either
CLEAR or PURGE for either database or both databases).

        CLEAR           Clears the volatile database at the local node.

        PURGE           Purges the permanent node database at the local
                        node.

        If the WITH qualifier is not specified, the node entries copied
        are added to the existing node database(s).

        NCP>COPY KNOWN NODES FROM LARK USING PERMANENT-
        _ TO PERMANENT WITH PURGE
        %NCP-I-NMLRSP, listener response - Success
        Remote node = 2.21 (Thrush)
        %NCP-I-RECDELET, Database entry deleted
        %NCP-I-NMLRSP, listener response - Success
        Remote node = 2.22 (Lark)
        %NCP-I-RECDELET, Database entry deleted
        %NCP-I-NMLRSP, listener response - Success
        Remote node = 2.20 (Robin)
        %NCP-I-RECDELET, Database entry deleted

        This copy command copies the node information from the
        permanent node database on node LARK into the permanent
        node database on the local node (ROBIN).  The node data-
        base is purged before the copy operation is begun.