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

3 SERVICE
Introduces a service parameter.

All underscores found in parameters must be replaced with spaces
when parameters are used in NCP commands.
 
4 DEVICE
indicates that the service device type is to be removed from
The database.

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

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

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

3 SOFTWARE
Introduces a software parameter.

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

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

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

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

3 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. 
!

2 OBJECT

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

CLEAR   KNOWN OBJECTS         (parameters...)
        OBJECT object-name

All underscores found in parameters must be replaced with spaces
when parameters are used in NCP commands.
 
3 KNOWN OBJECTS
Indicates that parameters for all known objects are to be
removed from the database.

3 OBJECT object-name
Identifies the object whose parameters are to be removed
from the database.

3 ACCOUNT
Removes from the volatile database the account control information.

3 ALIAS

4 INCOMING
Removes from the volatile database the ALIAS INCOMING parameter
for the specified object or all known objects.  Does not apply to
VAX PSI.

4 OUTGOING
Removes from the volatile database the ALIAS OUTGOING parameter
for the specified object or all known objects.  Does not apply to
VAX PSI.

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

3 FILE
Removes the name of the object's startup command file from the data base.

3 OUTGOING CONNECT PRIVILEGES
Removes the privileges required to make outbound connections to the object.
Does not apply to VAX PSI.

3 PASSWORD
Removes the password access control information from the data base.

3 PRIVILEGES
Removes the privileges required to access the object from the data base.
Does not apply to VAX PSI.

3 PROXY
Removes the proxy access information for the object from the data base.
Does not apply to VAX PSI.

3 USER
Removes the user access control information from the data base.

3 Examples

     NCP>CLEAR OBJECT DTR ALL

         This command removes all parameter entries for the DTR object
         in the volatile database.  As a result, the object no longer
         exists for the executor.
!