Use the CLEAR command to remove or reset selected parameters or components from the volatile database on the local node or DTE. Use the PURGE command to remove selected parameters or components from the permanent database on the local node or DTE.
1 – CIRCUIT
The CLEAR CIRCUIT command resets circuit parameters in the volatile
database to the default value (if any), or removes them from the volatile
database on the local node or DTE.
The PURGE CIRCUIT command always removes circuit parameters from the
permanent database on the local node or DTE.
CLEAR KNOWN CIRCUITS (parameters...)
CIRCUIT circuit-id
All underscores found in parameters must be replaced with spaces when
parameters are used in NCP commands.
1.1 – KNOWN CIRCUITS
Resets to the default value (if any) or removes from the volatile database the parameters for all known circuits.
1.2 – CIRCUIT circuit-id
Resets to the default value (if any) or removes from the volatile database the parameters for a specific circuit. Circuit-id specifies the name of the circuit you want to clear.
1.3 – ACTIVE
Differentiates between the active, inactive and dying DDCMP timer parameters.
1.3.1 – BASE
Applies only to DDCMP CONTROL circuits. Resets to its default value the ACTIVE BASE value in the volatile database.
1.3.2 – INCREMENT
Applies only to DDCMP CONTROL circuits. Resets to its default value the ACTIVE INCREMENT value in the volatile database.
1.4 – ALL
Removes from the volatile database the specified circuit or all known circuits. The circuit must be in the OFF state before you can specify this parameter.
1.5 – BABBLE TIMER
Applies only to DDCMP CONTROL circuits. Resets to its default value the BABBLE TIMER value in the volatile database.
1.6 – COUNTER TIMER
Cancels the logging timer. This cancellation prevents any further circuit counter logging for the indicated circuit or circuits.
1.7 – DEAD THRESHOLD
Applies only to DDCMP CONTROL circuits. Resets to its default value the DEAD THRESHOLD value in the volatile database.
1.8 – DYING
Differentiates between the active, inactive and dying DDCMP timer parameters.
1.8.1 – BASE
Applies only to DDCMP CONTROL circuits. Resets to its default value the DYING BASE value in the volatile database.
1.8.2 – INCREMENT
Applies only to DDCMP CONTROL circuits. Resets to its default value the DYING INCREMENT value in the volatile database.
1.8.3 – THRESHOLD
Applies only to DDCMP CONTROL circuits. Resets to its default value the DYING THRESHOLD value in the volatile database.
1.9 – INACTIVE
Differentiates between the active, inactive and dying DDCMP timer parameters.
1.9.1 – BASE
Applies only to DDCMP CONTROL circuits. Resets to its default value the INACTIVE BASE value in the volatile database.
1.10 – INCREMENT
Applies only to DDCMP CONTROL circuits. Resets to its default value the INACTIVE INCREMENT value in the volatile database.
1.11 – THRESHOLD
Applies only to DDCMP CONTROL circuits. Resets to its default value the INACTIVE THRESHOLD value in the volatile database.
1.12 – MAXIMUM
This modifier indicates an upper limit on a variety of parameters.
1.12.1 – BUFFERS
Applies only to DDCMP CONTROL circuits. Resets to its default value the MAXIMUM BUFFERS value in the volatile database.
1.12.2 – RECALLS
Applies only to X25 DLM circuits. Resets to its default value the limit on the number of call retries.
1.12.3 – ROUTERS
Applies only to broadcast circuits. Resets to its default value the MAXIMUM ROUTER value in the volatile database.
1.12.4 – TRANSMITS
Applies only to DDCMP CONTROL circuits. Resets to its default value the MAXIMUM TRANSMITS value in the volatile database.
1.13 – NETWORK
Applies only to purging X25 PVCs and X25 DLM circuits. Removes the circuit's network parameters from the permanent database.
1.14 – RECALL TIMER
Applies only to X25 DLM circuits. Resets to its default value the RECALL TIMER value in the volatile database.
1.15 – ROUTER PRIORITY
Applies only to broadcast circuits. Resets to its default value the priority assigned to the router in the volatile database.
1.16 – TRANSMIT TIMER
Applies only to DDCMP CONTROL circuits. Resets to its default value the TRANSMIT TIMER value in the volatile database.
1.17 – Examples
NCP>CLEAR CIRCUIT DMC-0 ALL
This command removes all parameter entries for circuit
DMC-0 in the volatile database. As a result, the circuit
no longer exists for the executor DECnet software.
2 – EXECUTOR
The CLEAR EXECUTOR command resets to the default the value (if any) or removes selected local node parameters from the volatile database on the local node. The PURGE EXECUTOR command removes selected local node parameters from the permanent database on the local node. You can not clear the BUFFER SIZE or STATE parameters from the volatile database. CLEAR EXECUTOR (parameters...) All underscores found in parameters must be replaced with spaces when parameters are used in NCP commands.
2.1 – ALIAS
Indicates that the parameter is among the set used for alias control.
2.1.1 – INCOMING
Removes from the volatile database the ALIAS INCOMING parameter for the local node.
2.1.2 – MAXIMUM LINKS
Removes from the volatile database the ALIAS MAXIMUM LINKS parameter for the local node.
2.1.3 – NODE
Removes from the volatile database the ALIAS NODE parameter for the local node.
2.2 – ALL
Applies only to purging the executor. Removes from the permanent database all executor parameters.
2.3 – AREA
Indicates that the parameter is used to control area routing. The possible parameters are AREA MAXIMUM COST and AREA MAXIMUM HOPS.
2.3.1 – MAXIMUM
2.3.1.1 – COST
Resets to its default value the AREA MAXIMUM COST value for the local node in the volatile database.
2.3.1.2 – HOPS
Resets to its default value the AREA MAXIMUM HOPS value for the local node in the volatile database.
2.4 – BROADCAST ROUTING TIMER
Resets to its default value the BROADCAST ROUTING TIMER value in the volatile database.
2.5 – BUFFER SIZE
Applies only to purging the executor. Removes from the permanent database the BUFFER SIZE parameter.
2.6 – COUNTER TIMER
Removes the volatile database the logging timer to prevents any further circuit counter logging for the local node.
2.7 – DELAY
2.7.1 – FACTOR
Resets to its default value the DELAY FACTOR value for the local node in the volatile database.
2.7.2 – WEIGHT
Resets to its default value the DELAY WEIGHT value for the local node in the volatile database.
2.8 – IDENTIFICATION
Removes from the volatile database the identification string for the local node.
2.9 – INACTIVITY TIMER
Resets to its default value the INACTIVITY TIMER value for the local node in the volatile database.
2.10 – INCOMING
2.10.1 – TIMER
Resets to its default value the INCOMING TIMER value for the local node in the volatile database.
2.10.2 – PROXY
Resets to its default value the INCOMING PROXY value for the local node in the volatile database.
2.11 – MAXIMUM
2.11.1 – ADDRESS
Resets to its default value the MAXIMUM ADDRESS value for the local node in the volatile database.
2.11.2 – AREA
Resets to its default value the MAXIMUM AREA value for the local node in the volatile database.
2.11.3 – BROADCAST
2.11.3.1 – NONROUTERS
Resets to its default value the MAXIMUM BROADCAST NONROUTERS value in the volatile database.
2.11.3.2 – ROUTERS
Resets to its default value the MAXIMUM BROADCAST ROUTERS in the volatile database.
2.11.4 – BUFFERS
Resets to its default value the MAXIMUM BUFFERS value for the local node in the volatile database.
2.11.5 – CIRCUITS
Resets to its default value the MAXIMUM CIRCUIT value for the local node in the volatile database.
2.11.6 – COST
Resets to its default value the MAXIMUM COSTS value for the local node in the volatile database.
2.11.7 – DECLARED OBJECTS
Resets to its default value the MAXIMUM DECLARED OBJECTS value for the local node in the volatile database.
2.11.8 – HOPS
Resets to its default value the MAXIMUM HOPS value for the local node in the volatile database.
2.11.9 – LINKS
Resets to its default value the MAXIMUM LINKS value for the local node in the volatile database.
2.11.10 – PATH SPLITS
Resets to its default value, the MAXIMUM PATH SPLITS value for the local node in the volatile database.
2.11.11 – VISITS
Resets to its default value the MAXIMUM VISITS value for the local node in the volatile database.
2.12 – NONPRIVILEGED item
Removes from the volatile database the specified nonprivileged access control information. Specify any or all of the following items for removal: ACCOUNT USER PASSWORD
2.13 – OUTGOING
2.13.1 – PROXY
Resets to its default value the OUTGOING PROXY value for the local node in the volatile database.
2.13.2 – TIMER
Resets to its default value the OUTGOING TIMER value for the local node in the volatile database.
2.14 – PATH SPLIT POLICY
Resets to its default value the PATH SPLIT POLICY parameter for the local node in the volatile database.
2.15 – PRIVILEGED item
Removes from the volatile database the specified privileged access control information. Specify any or all of the following items for removal: ACCOUNT USER PASSWORD
2.16 – RETRANSMIT FACTOR
Resets to its default value the RETRANSMIT FACTOR value for the local node in the volatile database.
2.17 – ROUTING TIMER
Resets to its default value the ROUTING TIMER value for the local node in the volatile database.
2.18 – SEGMENT BUFFER SIZE
Resets to its default value the SEGMENT BUFFER SIZE value for the local node in the volatile database.
2.19 – STATE
Applies only to purging the executor. Removes from the permanent database the local node's state.
2.20 – SUBADDRESSES
Removes from the volatile database the value of the range of local DTE subaddresses.
2.21 – Examples
NCP>CLEAR EXECUTOR NAME IDENTIFICATION
This command removes the local node's name and identification
string from the volatile database.
NCP>CLEAR EXECUTOR DELAY FACTOR
This command removes delay factor from the volatile database
which causes the software to use the default value.
2.22 – NODE
The CLEAR EXECUTOR NODE command clears the default executor designation for all NCP commands. The executor of commands becomes the local node. The TELL prefix cannot be used with this command. After you issue the CLEAR EXECUTOR NODE command, NML, linked with NCP on the local node, will perform all NML operations. NML uses the privileges of your current process instead of the default nonprivileged accounts. CLEAR EXECUTOR NODE
2.22.1 – Examples
NCP>SET EXECUTOR NODE TRNTO
...
NCP>CLEAR EXECUTOR NODE
3 – LINE
Use the CLEAR LINE command to remove line parameters (or reset the
parameters to their default values) from the volatile database on
the executor node. For an X25 line, the default value depends on the
NETWORK parameter in the permanent database. Use the PURGE LINE
command to remove line parameters from the permanent database on
the executor node.
CLEAR KNOWN LINES (parameters...)
LINE line-id
All underscores found in parameters must be replaced with spaces
when parameters are used in NCP commands.
3.1 – KNOWN LINES
Resets to the default (if any) or removes the parameters for all known lines from the volatile database.
3.2 – LINE line-id
Identifies the specific line whose parameters are to be reset to their default values (if any) or removed from the volatile database.
3.3 – ALL
Removes the specified line or all known lines from the volatile database. The line must be in the OFF state before you specify this parameter.
3.4 – COUNTER TIMER
Resets the logging timer to zero. This prevents any further line counter logging for the indicated line(s).
3.5 – DEAD TIMER
Applies only to DDCMP lines. Resets to its default the DEAD TIMER parameter in the volatile database.
3.6 – DELAY TIMER
Applies only to DDCMP lines. Resets to its default the DELAY TIMER parameter in the volatile database.
3.7 – ECHO
3.7.1 – DATA
Applies only to FDDI lines. Resets to its default the ECHO DATA parameter in the volatile database. Permanent database operations cannot be performed on this parameter.
3.7.2 – LENGTH
Applies only to FDDI lines. Resets to its default the ECHO LENGTH parameter in the volatile database. Permanent database operations cannot be performed on this parameter.
3.7.3 – TARGET
Applies only to FDDI lines. Resets to its default the ECHO TARGET parameter in the volatile database. Permanent database operations cannot be performed on this parameter.
3.8 – HANGUP
Applies only to asynchronous DDCMP lines. Removes from the volatile database the HANGUP state of the line.
3.9 – INTERFACE
Applies only to X25 lines. Resets the INTERFACE parameter to the default value of DTE.
3.10 – LINE SPEED
Applies only to asynchronous DDCMP lines. Removes from the volatile database the Line Speed parameter.
3.11 – MAXIMUM RETRANSMITS
Applies only to X25 lines. Resets the maximum number of retransmissions of a frame to the default value for the specified line or all known lines in the volatile database.
3.12 – NETWORK
Applies only to X25 lines. Removes the NETWORK parameter from the permanent database.
3.13 – NIF TARGET
Applies only to FDDI lines. Resets to its default value the NIF TARGET parameter in the volatile database. Permanent database operations cannot be performed on this parameter.
3.14 – RECEIVE BUFFERS
Applies only to DDCMP lines. Resets to its default value the RECEIVE BUFFERS parameter in the volatile database.
3.15 – REQUESTED TRT
Applies only to FDDI lines. Resets to its default value the REQUESTED TRT parameter in the volatile database.
3.16 – RESTRICTED TOKEN TIMEOUT
Applies only to FDDI lines. Resets to its default value the RESTRICTED TOKEN TIMEOUT parameter in the volatile database.
3.17 – RING PURGER ENABLE
Applies only to FDDI lines. Resets to its default value the RING PURGER ENABLE parameter in the volatile database.
3.18 – SCHEDULING TIMER
Applies only to DDCMP lines. Resets to its default value the SCHEDULING TIMER parameter in the volatile database.
3.19 – SIF
3.19.1 – CONFIGURATION TARGET
Applies only to FDDI lines. Resets to its default value the SIF CONFIGURATION TARGET parameter in the volatile database. Permanent database operations cannot be performed on this parameter.
3.19.2 – OPERATION TARGET
Applies only to FDDI lines. Resets to its default value the SIF OPERATION TARGET parameter in the volatile database. Permanent database operations cannot be performed on this parameter.
3.20 – STREAM TIMER
Applies only to DDCMP lines. Resets to its default value the STREAM TIMER parameter in the volatile database.
3.21 – SWITCH
Applies only to asynchronous DDCMP lines. Removes from the volatile database the SWITCH parameter.
3.22 – TRANSMIT PIPELINE
Applies only to DMR11 lines. Removes from the volatile database the TRANSMIT PIPELINE parameter.
3.23 – VALID TRANSMISSION TIME
Applies only to FDDI lines. Resets to its default value the VALID TRANSMISSION TIME parameter in the volatile database.
3.24 – Examples
NCP>CLEAR LINE DMC-0 ALL
This command removes line DMC-0 from the volatile database.
NCP>CLEAR KNOWN LINES MAXIMUM RETRANSMITS
This command resets the maximum number of retransmissions of
a frame for all known lines in the volatile database. The
parameter is reset to its default value.
4 – LOGGING
Use the CLEAR LOGGING command to remove logging parameters from the
volatile database on the executor node. Use the PURGE LOGGING command
to remove logging parameters from the permanent database on the executor
node.
CLEAR KNOWN LOGGING ALL
LOGGING CONSOLE EVENTS event-list
LOGGING FILE KNOWN EVENTS
LOGGING MONITOR AREA area-number
CIRCUIT circuit-id
LINE line-id
MODULE name
NAME
NODE node-id
SINK EXECUTOR
NODE node-id
All underscores found in parameters must be replaced with spaces
when parameters are used in NCP commands.
4.1 – ALL
Indicates that all logging parameters for the specified component are to be removed from the database. The component is no longer recognized by the network.
4.2 – EVENTS event-list
Identifies the class and types of events to be removed from the database. See HELP EVENTS for a list of valid events.
4.3 – KNOWN
Introduces a plural parameter or component.
4.3.1 – EVENTS
Indicates that the event filter is to be removed from the specified logging component.
4.3.2 – LOGGING
Indicates that the parameters for all known logging are to be removed from the database.
4.4 – AREA area-number
Indicated the area to which the events apply. Events will not be logged for this source.
4.5 – CIRCUIT circuit-id
Identifies the circuit to which the events apply. Events will not be logged for this source.
4.6 – LINE line-id
Identifies the line to which the events apply. Events will not be logged for this source.
4.7 – CONSOLE
Indicates that the parameters for logging to the console are to be removed from the database.
4.8 – FILE
Indicates that the parameters for logging to a file are to be removed from the database.
4.9 – MODULE
Introduces a MODULE parameter.
4.9.1 – X25-ACCESS
Removes all logging parameters for the specified logging source from the data base.
4.9.2 – X25-PROTOCOL
Removes all logging parameters for the specified logging source from the data base.
4.9.3 – X25-SERVER
Removes all logging parameters for the specified logging source from the data base.
4.9.4 – X29-SERVER
Removes all logging parameters for the specified logging source from the data base.
4.10 – MONITOR
Indicates that the parameters for logging to a monitor program are to be removed from the database.
4.11 – NAME
Indicates that the NAME parameter is to be removed from the database. This is the name of the console, file or monitor program.
4.12 – NODE node-id
Identifies the node to which the events apply. Events will not be logged for this source.
4.13 – SINK
Identifies the node where the event logger runs to log the events.
There are two possibilities:
NODE node-id identifies the node at which
events are being logged.
EXECUTOR identifies the executor node.
Only events being logged to this node are removed from the
database. If this parameter is omitted, the executor node is
assumed to be the sink node affected.
4.14 – Examples
NCP>CLEAR LOGGING FILE EVENTS 2.*
This command clears logging for all class 2 events to the
logging file.
5 – MODULE
Introduces the various module entities.
5.1 – CONFIGURATOR
Use CLEAR MODULE CONFIGURATOR command to remove from the volatile database the Ethernet module configurator parameters for all circuits. The word MODULE is optional. CLEAR MODULE CONFIGURATOR KNOWN CIRCUITS ALL
5.2 – X25-ACCESS
Use the CLEAR MODULE X25-ACCESS command to remove from the volatile
database network names and parameters used by the host node to
access a specified X25 network or networks through a multi-host
node. The multi-host node serving as a gateway to the specified
X25 network must be a VMS node with VAX PSI multi-host software
installed. Use the PURGE MODULE X25-ACCESS command to remove these
same network names and parameters from the permanent database.
CLEAR MODULE X25-ACCESS NETWORK network-name ACCOUNT
KNOWN NETWORKS ALL
PASSWORD
USER
All underscores found in parameters must be replaced with spaces
when parameters are used in NCP commands.
5.2.1 – ACCOUNT
removes the account from the data base for the specified network or all known networks.
5.2.2 – ALL
Removes all parameters for the specified network or all known networks in the data base.
5.2.3 – KNOWN NETWORKS
Identifies all known networks
5.2.4 – NETWORK network-name
Identifies the network whose parameters are to be removed from the data base.
5.2.5 – PASSWORD
Removes the password from the data base for the specified network or all known networks.
5.2.6 – USER
Removes the user identification from the data base for the specified network or all known networks.
5.3 – X25-PROTOCOL
Use the CLEAR MODULE X25-PROTOCOL command to remove the parameters of
the Protocol Module component from the volatile database.
CLEAR MODULE X25-PROTOCOL DTE dte-address NETWORK network-name
KNOWN DTES KNOWN NETWORKS
CALL TIMER
CLEAR TIMER
COUNTER TIMER
INTERRUPT TIMER
MAXIMUM CLEARS
MAXIMUM RESETS
MAXIMUM RESTARTS
RESET TIMER
RESTART TIMER
GROUP group-name ALL
KNOWN GROUPS
NETWORK net-name ALL
KNOWN NETWORKS
All underscores found in parameters must be replaced with spaces
when parameters are used in NCP commands.
5.3.1 – ALL
Can be used with DTE, GROUP or NETWORK. It removes all parameters for the specified component or for all known DTEs, groups or networks.
5.3.2 – KNOWN
Can be used with DTES, NETWORKS and GROUPS. KNOWN DTES selects all known DTEs on the network specified or all known networks. KNOWN NETWORKS selects all known networks. KNOWN GROUPS selects all known groups.
5.3.3 – DTE dte-address
Removes parameters for the specified DTE. If you use this qualifier you must associate it with the NETWORK parameter or KNOWN NETWORKS parameter to identify the network or networks to which the DTE belongs.
5.3.3.1 – GROUPS
Remove the parameters for all known groups.
5.3.4 – NETWORK network-name
Can be used as a qualifier or as a parameter in conjunction with the DTE qualifier. As a qualifier it removes all DTEs, groups and parameters for the specified network. The ALL parameter is mandatory.
5.3.5 – DTE dte-address
The DTE address is a decimal integer of 1 to 15 digits.
5.3.6 – GROUP group-name
Specifies the closed user group (CUG) or bilateral closed user group (BCUG).
5.3.7 – COUNTER TIMER
Resets the counter timer to zero for the specified DTE or all known DTEs in the volatile data base.
5.3.8 – CALL TIMER
If used with the CLEAR command, resets the call timer in the volatile data base to its default value; if used with the PURGE command, resets the call timer in the permanent data base to 0. This means that the call request will not time out at the local DTE, but may be cleared by the network.
5.3.9 – CLEAR TIMER
If used with the CLEAR command, resets the clear timer in the volatile data base to its default value; if used with the PURGE command, resets the clear timer in the permanent data base to prevent retransmission of a request to clear a virtual circuit.
5.3.10 – MAXIMUM
5.3.10.1 – CLEARS
If used with the CLEAR command, resets the maximum number of attempts to clear a circuit to the default value in the volatile data base; if used with the PURGE command, resets the maximum number so that there is no maximum in the permanent data base.
5.3.10.2 – RESETS
If used with the CLEAR command, resets the maximum number of attempts to reset a circuit to the default value in the volatile data base; if used with the PURGE command, resets the maximum number so that there is no maximum in the permanent data base.
5.3.10.3 – RESTARTS
If used with the CLEAR command, resets the maximum number of attempts to restart a virtual circuit to the default value in the volatile data base; if used with the PURGE command, resets the maximum number so that there is no maximum in the permanent data base.
5.3.11 – RESET TIMER
If used with the CLEAR command, resets the timer in the volatile data base to its default value; if used with the PURGE command, resets the timer in the permanent data base to prevent retransmission of a reset.
5.3.12 – RESTART TIMER
If used with the CLEAR command, resets the timer in the volatile data base to its default value; if used with the PURGE command, resets the timer in the permanent data base to prevent retransmission of a restart.
5.4 – X25-SERVER
Use the CLEAR MODULE X25-SERVER command to remove the parameters
of the X25 Call Handler from the volatile data base.
CLEAR MODULE X25-SERVER COUNTER TIMER
X29-SERVER
DESTINATION dest-name ACCOUNT
KNOWN DESTINATIONS ALL
CALL MASK
CALL VALUE
CALLED ADDRESS
EXTENSION MASK
EXTENSION VALUE
GROUP
INCOMING ADDRESS
NETWORK
PASSWORD
PRIORITY
RECEIVING DTE
REDIRECT REASON
SENDING ADDRESS
SUBADDRESSES
USER
For additional help see the CLEAR MODULE X25-SERVER command which
is identical in format to the PURGE MODULE X25-SERVER command.
All underscores found in parameters must be replaced with spaces
when parameters are used in NCP commands.
5.4.1 – ACCOUNT
Removes the account from the data base for the specified destination or all known destinations.
5.4.2 – ALL
Removes all parameters for the specified destination or all known destinations in the data base.
5.4.3 – KNOWN DESTINATIONS
Identifies all known destinations.
5.4.4 – DESTINATION dest-name
Identifies the destination whose parameters are to be removed from the data base.
5.4.5 – CALL
5.4.5.1 – MASK
Removes the call mask from the data base for the specified destination or all known destinations.
5.4.5.2 – VALUE
Removes the call value from the data base for the specified destination or all known destinations.
5.4.6 – CALLED ADDRESS
Removes from the volatile database the called DTE address for the specified destination or all known destinations.
5.4.7 – COUNTER TIMER
Resets the module counter timer to zero.
5.4.8 – EXTENSION
5.4.8.1 – MASK
Removes from the volatile database the extension mask for the specified destination or all known destinations.
5.4.8.2 – VALUE
Removes from the volatile database the extension value for the specified destination or all known destinations.
5.4.9 – GROUP
Removes the group name from the data base for the specified destination or all known destinations.
5.4.10 – INCOMING ADDRESS
Removes from the volatile database the incoming address for the specified destination or all known destinations.
5.4.11 – NETWORK
Removes from the volatile database the network name for the specified destination or all known destinations.
5.4.12 – PASSWORD
Removes the password from the data base for the specified destination or all known destinations.
5.4.13 – PRIORITY
Resets the priority to the lowest value for the specified destination or all known destinations.
5.4.14 – RECEIVING DTE
Removes from the volatile database the receiving DTE address for the specified destination or all known destinations.
5.4.15 – REDIRECT REASON
Removes from the volatile database the redirect reason code for the specified destination or all known destinations.
5.4.16 – SENDING ADDRESS
Removes from the volatile database the sending DTE address for the specified destination or for all known destinations.
5.4.17 – SUBADDRESSES
Removes the subaddress range from the data base for the specified destination or all known destinations.
5.4.18 – USER
Removes the user identification from the data base for the specified destination or all known destinations.
5.5 – X29-SERVER
Use the CLEAR MODULE X29-SERVER command to remove the parameters
of the X.29 Call Handler from the permanent data base.
CLEAR MODULE X25-SERVER COUNTER TIMER
X29-SERVER
DESTINATION dest-name ACCOUNT
KNOWN DESTINATIONS ALL
CALL MASK
CALL VALUE
CALLED ADDRESS
EXTENSION MASK
EXTENSION VALUE
GROUP
INCOMING ADDRESS
NETWORK
PASSWORD
PRIORITY
RECEIVING DTE
REDIRECT REASON
SENDING ADDRESS
SUBADDRESSES
USER
For additional help see the CLEAR MODULE X29-SERVER command which
is identical in format to the PURGE MODULE X29-SERVER command.
6 – NODE
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.
6.1 – KNOWN NODES
Indicates that the specified parameters for all known nodes are to be removed from the database.
6.2 – NODE node-id
Identifies the node whose parameters are to be removed from the database.
6.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.
6.4 – CIRCUIT
Indicates that the loop node parameter associated with the circuit is to be removed from the database.
6.5 – COUNTER TIMER
Indicates that the counter timer value is to be removed from the database.
6.6 – CPU
Indicates that the node's CPU identification is to be removed from the database.
6.7 – DIAGNOSTIC FILE
Removes from the volatile database the identification of the downline loading diagnostics file.
6.8 – DUMP
6.8.1 – ADDRESS
Removes the up-line dump address of the adjacent node from the data base.
6.8.2 – COUNT
Removes the up-line dump count from the data base.
6.8.3 – FILE
Removes the up-line dump file identification from the data base.
6.9 – HARDWARE ADDRESS
Removes from the volatile database the hardware address.
6.10 – HOST
Indicates that the identification of the host node is to be removed from the database.
6.11 – INBOUND
Applies only to nodes on dynamic asynchronous DDCMP circuits. Removes the INBOUND parameter from the database.
6.12 – LOAD
6.12.1 – ASSIST
6.12.1.1 – AGENT
Removes from the volatile database the identification of the VMS image used to assist a downline load.
6.12.1.2 – PARAMETER
Removes from the volatile database the identification of the value to be passed to the load assist agent.
6.13 – LOAD FILE
Indicates that the identification of the downline loading file is to be removed from the database.
6.14 – MANAGEMENT FILE
Removes from the volatile database the identification of the downline loading management information file.
6.15 – NAME
Indicates that the node name parameter for the node address is to be removed from the database.
6.16 – NONPRIVILEGED
Indicates that the specified nonprivileged access control information is to be removed from the database. ACCOUNT, PASSWORD, and USER can follow.
6.17 – PRIVILEGED
Indicates that the specified privileged access control information is to be removed from the database. ACCOUNT, PASSWORD, and USER can follow.
6.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.
6.19 – SECONDARY LOADER
Indicates that the identification of the secondary downline loading file is to be removed from the database.
6.20 – SERVICE
Introduces a service parameter. All underscores found in parameters must be replaced with spaces when parameters are used in NCP commands.
6.20.1 – DEVICE
indicates that the service device type is to be removed from The database.
6.20.2 – CIRCUIT
Indicates that the circuit parameter associated with the node for downline loading purposes is to be removed from the database.
6.20.3 – NODE VERSION
Indicates that the service node version parameter is to be removed from the database.
6.20.4 – PASSWORD
Indicates that the password parameter required to trigger the bootstrap mechanism is to be removed from the database.
6.21 – SOFTWARE
Introduces a software parameter.
6.21.1 – IDENTIFICATION
Indicates that the identification of the software is to be removed from the database.
6.21.2 – TYPE
Indicates that the initial load software program type is to be removed from the database.
6.22 – TERTIARY LOADER
Indicates that the identification of the tertiary downline loading file is to be removed from the database.
6.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.
6.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.
7 – 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.
7.1 – KNOWN OBJECTS
Indicates that parameters for all known objects are to be removed from the database.
7.2 – OBJECT object-name
Identifies the object whose parameters are to be removed from the database.
7.3 – ACCOUNT
Removes from the volatile database the account control information.
7.4 – ALIAS
7.4.1 – INCOMING
Removes from the volatile database the ALIAS INCOMING parameter for the specified object or all known objects. Does not apply to VAX PSI.
7.4.2 – OUTGOING
Removes from the volatile database the ALIAS OUTGOING parameter for the specified object or all known objects. Does not apply to VAX PSI.
7.5 – 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.
7.6 – FILE
Removes the name of the object's startup command file from the data base.
7.7 – OUTGOING CONNECT PRIVILEGES
Removes the privileges required to make outbound connections to the object. Does not apply to VAX PSI.
7.8 – PASSWORD
Removes the password access control information from the data base.
7.9 – PRIVILEGES
Removes the privileges required to access the object from the data base. Does not apply to VAX PSI.
7.10 – PROXY
Removes the proxy access information for the object from the data base. Does not apply to VAX PSI.
7.11 – USER
Removes the user access control information from the data base.
7.12 – 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.