Use the CLEAR NODE command to remove node parameters from the volatile
 database  on  the  executor node.  Use the PURGE NODE command to remove
 node parameters from the permanent database on the executor node.

 CLEAR   KNOWN NODES     (parameters ...)
         NODE node-id

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

1  –  KNOWN NODES

 Indicates that the specified parameters for all known nodes
 are to be removed from the database.

2  –  NODE node-id

 Identifies the node whose parameters are to be removed from
 the database.

3  –  ALL

 Indicates that parameters for the specified node or all
 known nodes are to be removed from the database. The
 component is no longer recognized by the network.

4  –  CIRCUIT

 Indicates that the loop node parameter associated with the
 circuit is to be removed from the database.

5  –  COUNTER TIMER

 Indicates that the counter timer value is to be removed from
 the database.

6  –  CPU

 Indicates that the node's CPU identification is to be removed
 from the database.

7  –  DIAGNOSTIC FILE

 Removes from the volatile database the identification of the downline
 loading diagnostics file.

8  –  DUMP

8.1  –  ADDRESS

 Removes the up-line dump address of the adjacent node from the
 data base.

8.2  –  COUNT

 Removes the up-line dump count from the data base.

8.3  –  FILE

 Removes the up-line dump file identification from the data base.

9  –  HARDWARE ADDRESS

 Removes from the volatile database the hardware address.

10  –  HOST

 Indicates that the identification of the host node is to be
 removed from the database.

11  –  INBOUND

 Applies only to nodes on dynamic asynchronous DDCMP circuits.  Removes
 the INBOUND parameter from the database.

12  –  LOAD

12.1  –  ASSIST

12.1.1  –  AGENT

 Removes from the volatile database the identification of the
 VMS image used to assist a downline load.

12.1.2  –  PARAMETER

 Removes from the volatile database the identification of the value
 to be passed to the load assist agent.

13  –  LOAD FILE

 Indicates that the identification of the downline loading
 file is to be removed from the database.

14  –  MANAGEMENT FILE

 Removes from the volatile database the identification of the
 downline loading management information file.

15  –  NAME

 Indicates that the node name parameter for the node address
 is to be removed from the database.

16  –  NONPRIVILEGED

 Indicates that the specified nonprivileged access control
 information is to be removed from the database.

 ACCOUNT, PASSWORD, and USER can follow.

17  –  PRIVILEGED

 Indicates that the specified privileged access control
 information is to be removed from the database.

 ACCOUNT, PASSWORD, and USER can follow.

18  –  RECEIVE PASSWORD

 Indicates that the receive password expected from the remote
 node during a Routing initialization sequence is to be
 removed from the database.

19  –  SECONDARY LOADER

 Indicates that the identification of the secondary downline
 loading file is to be removed from the database.

20  –  SERVICE

 Introduces a service parameter.

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

20.1  –  DEVICE

 indicates that the service device type is to be removed from
 The database.

20.2  –  CIRCUIT

 Indicates that the circuit parameter associated with the node
 for downline loading purposes is to be removed from the
 database.

20.3  –  NODE VERSION

 Indicates that the service node version parameter is to be
 removed from the database.

20.4  –  PASSWORD

 Indicates that the password parameter required to trigger
 the bootstrap mechanism is to be removed from the database.

21  –  SOFTWARE

 Introduces a software parameter.

21.1  –  IDENTIFICATION

 Indicates that the identification of the software is to be
 removed from the database.

21.2  –  TYPE

 Indicates that the initial load software program type is to
 be removed from the database.

22  –  TERTIARY LOADER

 Indicates that the identification of the tertiary downline
 loading file is to be removed from the database.

23  –  TRANSMIT PASSWORD

 Indicates that the transmit password sent to the remote node
 during a Routing initialization sequence is to be removed
 from the database.

24  –  Examples

      NCP>CLEAR NODE TRNTO ALL

          This command removes all parameter entries for node TRNTO in
          the volatile database.  As a result, the node no longer
          exists for executor DECnet software.

      NCP>CLEAR NODE 14 NAME DENVER
      ...

      NCP>SET NODE 15 NAME DENVER

          The first command disassociates the name DENVER with node 1.14.
          The second command associates the same name with node 1.15.
          Note that the default area number 1 is assumed if no area
          number is specified.