% Librarian T09-20!.?Je.?JZ5 CLEARuCommands{RCONNECTCOPYDEFINE DISCONNECTVEVENTSEXITZHELP LISTLOAD LOOP Parameters& PromptingvPURGESETSHOW*TELL TRIGGERZERO] ,1 CLEARJUse the CLEAR command to remove or reset selected parameters or components6from the volatile database on the local node or DTE. JUse the PURGE command to remove selected parameters or components from the,permanent database on the local node or DTE. ! 2 CIRCUITDThe CLEAR CIRCUIT command resets circuit parameters in the volatile Jdatabase to the default value (if any), or removes them from the volatile database. -CLEAR KNOWN CIRCUITS  (parameters...) CIRCUIT circuit-idEThe PURGE CIRCUIT command always removes circuit parameters from the permanent database.-PURGE KNOWN CIRCUITS (parameters...) CIRCUIT circuit-idFAll underscores found in parameters must be replaced with spaces when $parameters are used in NCP commands. 3 ACTIVE_BASEGApplies only to DDCMP CONTROL circuits. Resets to its default value theFACTIVE BASE value in the volatile database, or removes the ACTIVE BASE"value from the permanent database.3 ACTIVE_INCREMENTHApplies only to DDCMP CONTROL circuits. Resets to its default value theGACTIVE INCREMENT value in the volatile database, or removes the ACTIVE ,INCREMENT value from the permanent database.3 ALLHRemoves from the database the specified circuit or all known circuits. IThe circuit must be in the OFF state before you can CLEAR this parameter.3 BABBLE TIMERHApplies only to DDCMP CONTROL circuits. Resets to its default value theHBABBLE TIMER value in the volatile database, or removes the value BABBLE"TIMER from the permanent database. 3 CIRCUIT circuit-idFResets to the default value (if any) or removes from the database the =parameters for a specific circuit. Circuit-id specifies the &name of the circuit you want to clear.3 COSTIDoes not apply to X.25 PVCs. Resets to its default value the COST value Ain the volatile database, or removes the COST parameter from the permanent database.3 COUNTER TIMERICancels the event logging timer. This cancellation prevents any further Dcircuit counter event logging for the indicated circuit or circuits.3 DEAD THRESHOLDHApplies only to DDCMP CONTROL circuits. Resets to its default value theCDEAD THRESHOLD value in the volatile database, or removes the DEAD ,THRESHOLD value from the permanent database.3 DTEFApplies only to DLM circuits. Allows the X.25 call to be set up usingany local DTE. 3 DYING_BASEHApplies only to DDCMP CONTROL circuits. Resets to its default value theEDYING BASE value in the volatile database, or removes the DYING BASE "value from the permanent database.3 DYING_INCREMENTHApplies only to DDCMP CONTROL circuits. Resets to its default value theDDYING INCREMENT value in the volatile database, or removes the DYING.INCREMENT value from the permanent database. 3 DYING_THRESHOLDHApplies only to DDCMP CONTROL circuits. Resets to its default value theDDYING THRESHOLD value in the volatile databa se, or removes the DYING,THRESHOLD value from the permanent database. 3 HELLO TIMERCDoes not apply to X.25 PVCs. Resets to its default value the HELLOFTIMER value in the volatile database, or removes the HELLO TIMER valuefrom the permanent database. 9 3 INACTIVE_BASEDApplies only to DDCMP CONTROL circuits. Resets to its default value@the INACTIVE BASE value in the volatile database, or removes the0INACTIVE BASE value fr om the permanent database.3 INACTIVE_INCREMENTDApplies only to DDCMP CONTROL circuits. Resets to its default valueEthe INACTIVE INCREMENT value in the volatile database, or removes the5INACTIVE INCREMENT value from the permanent database.3 INACTIVE_THRESHOLDDApplies only to DDCMP CONTROL circuits. Resets to its default valueEthe INACTIVE THRESHOLD value in the volatile database, or removes the5INACTIVE THRESHOLD value from the permanent database.3 KNOWN CIRCUITSFResets t o the default value (if any) or removes from the database the "parameters for all known circuits.3 MAXIMUM_BUFFERSDApplies only to DDCMP CONTROL circuits. Resets to its default valueBthe MAXIMUM BUFFERS value in the volatile database, or removes the2MAXIMUM BUFFERS value from the permanent database.3 MAXIMUM_RECALLSCApplies only to X.25 DLM circuits. Resets to its default value theAlimit on the number of call retries in the volatile database, or?removes the MAXIMUM RECALLS v alue from the permanent database.3 MAXIMUM_ROUTERSDApplies only to broadcast circuits. Resets to its default value theFMAXIMUM ROUTERS value in the volatile database, or removes the MAXIMUM*ROUTERS value from the permanent database.3 MAXIMUM_TRANSMITSDApplies only to DDCMP CONTROL circuits. Resets to its default valueDthe MAXIMUM TRANSMITS value in the volatile database, or removes the4MAXIMUM TRANSMITS value from the permanent database. 3 NETWORKEApplies only to purging X.25 PVCs and X.25 DLM circuits. Removes the9circuit's network parameters from the permanent database.3 NUMBERCApplies only to incoming DLM circuits. Removes the restriction on 9accepting calls only from a particular remote DTE number.3 RECALL TIMERCApplies only to X.25 DLM circuits. Resets to its default value theBRECALL TIMER value in the volatile database, or removes the RECALL(TIMER value from the permanent database. 3 ROUTER PRIORITYEApplies only to broadcast circuits. Resets to its default value the Dpriority assigned to the router in the volatile database, or removes6the ROUTER PRIORITY value from the permanent database.3 TRANSMIT TIMERDApplies only to DDCMP CONTROL circuits. Resets to its default valueAthe TRANSMIT TIMER value in the volatile database, or removes the1TRANSMIT TIMER value from the permanent database. 3 Examples NCP>CLEAR CIRCUIT DMC-0 ALL? This command removes all parameter entries for circuitC  DMC-0 in the volatile database. As a result, the circuit ; no longer exists for the executor DECnet software., NCP>CLEAR CIRCUIT DMP-0.4 COUNTER TIMERE This command removes the COUNTER TIMER parameter for circuit, DMP-0.4 from the volatile database.% NCP>PURGE CIRCUIT X25-ANDIES ALLD This command removes all parameter entries in the permanentE database for the X.25 permanent virtual circuit (PVC) called X25-ANDIES. NCP>CLEAR CIRCUIT UNA-* ALL@ This command clears all UNA circuits and the associatedB parameters for all UNA circuits in the volatile database. NCP>PURGE CIRCUIT DMC-0 ALLE This command removes all parameter entries for circuit DMC-0# in the permanent database.! 2 EXECUTORFThe CLEAR EXECUTOR command resets to the default the value (if any) orIremoves selected local node parameters from the volatile database on theDlocal node. You  can not clear the BUFFER SIZE, SEGMENT BUFFER SIZE,CMAXIMUM BROADCAST ROUTERS, ALIAS NODE, or STATE parameters from theBvolatile database when the executor is in the ON state. 'CLEAR EXECUTOR (parameters...)2The PURGE EXECUTOR command removes selected local >node parameters from the permanent database on the local node. 'PURGE EXECUTOR (parameters...)@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ALIAS_INCOMINGDRemoves from the database the ALIAS INCOMING parameter for the localnode.3 ALIAS_MAXIMUM_LINKSEResets to its default value ALIAS MAXIMUM LINKS value in the volatileEdatabase, or removes the ALIAS MAXIMUM LINKS value from the permanent database. 3 ALIAS_NODEBApplies only to purging the executor. Removes from the permanent 5database the ALIAS NODE parameter for the local node.3 ALLAApplies only to purging the executor. Removes from the permanent!database all executor parameters.3 AREA_MAXIMUM_COSTEResets to its default value the AREA MAXIMUM COST value for the localEnode in the volatile database, or removes the AREA MAXIMUM COST valuefrom the permanent database.3 AREA_MAXIMUM_HOPSEResets to its default value the AREA MAXIMUM HOPS value for the localEnode in the volatile database, or removes the AREA MAXIMUM HOPS valuefrom the permanent database.3 BROADCAST ROUTING TIMERDResets to its default value the BROADCAST ROUTING TIMER value in theDvolatile database, or removes the BROADCAST ROUTING TIMER value fromthe permanent database. 3 BUFFER SIZEAApplies only to purging the executor. Removes from the permanent#database the BUFFER SIZE parameter.3 COUNTER TIMERARemoves from the database the COUNTER TIMER parameter to prevent +further counter logging for the local node.3 DEFAULT ACCESSDResets to its default value the DEFAULT ACCESS value in the volatile@database, or removes the DEFAULT ACCESS value from the permanent database. 3 DELAY_FACTORFResets to its default value the DELAY FACTOR value for the local node Din the volatile database, or removes the DELAY FACTOR value from thepermanent database.3 DELAY_WEIGHTFResets to its default value the DELAY WEIGHT value for the local node Din the volatile database, or removes the DELAY WEIGHT value from thepermanent database.3 DNS_INTERFACE6Removes from the database the DNS INTERFACE parameter.3 DNS_NAMESPACE6Removes from the database the DNS NAMESPACE parameter.3 IDENTIFICATION<Removes from the database the identification string for the local node.3 IDP,Removes from the database the IDP parameter.3 INACTIVITY TIMERDResets to its default value the INACTIVITY TIMER value for the localDnode in the volatile database, or removes the INACTIVITY TIMER valuefrom the permanent database.3 INCOMING_PROXYBResets to its default value the INCOMING PROXY value for the localBnode in the volatile database, or removes the INCOMING PROXY valuefrom the permanent database.3 INCOMING_TIMERBResets to its default value the INCOMING TIMER value for the localBnode in the volatile database, or removes the INCOMING TIMER valuefrom the permanent database.3 MAXIMUM_ADDRESSCResets to its default value the MAXIMUM ADDRESS value for the localCnode in the volatile database, or removes the MAXIMUM ADDRESS valuefrom the permanent database.3 MAXIMUM_AREAERese ts to its default value the MAXIMUM AREA value for the local nodeDin the volatile database, or removes the MAXIMUM AREA value from thepermanent database.3 MAXIMUM_BROADCAST_NONROUTERS<Resets to its default value the MAXIMUM BROADCAST NONROUTERS@value in the volatile database, or removes the MAXIMUM BROADCAST-NONROUTERS value from the permanent database.3 MAXIMUM_BROADCAST_ROUTERSDApplies only to purging the executor. Removes the MAXIMUM BROADCAST*ROUTERS value from the permanent database.3 MAXIMUM_BUFFERS>Removes the MAXIMUM BUFFERS value from the permanent database.3 MAXIMUM_CIRCUITSDResets to its default value the MAXIMUM CIRCUITS value for the localEnode in the volatile database, or removes the MAXIMUM CIRCUITS value from the permanent database.3 MAXIMUM_COST@Resets to its default value the MAXIMUM COST value for the localEnode in the volatile database, or removes the MAXIMUM COST value fromthe permanent database.3 MAXIMUM_DECLARED_OBJECTSBRese ts to its default value the MAXIMUM DECLARED OBJECTS value for?the local node in the volatile database, or removes the MAXIMUM3DECLARED OBJECTS value from the permanent database.3 MAXIMUM_HOPS@Resets to its default value the MAXIMUM HOPS value for the localEnode in the volatile database, or removes the MAXIMUM HOPS value fromthe permanent database.3 MAXIMUM_LINKSAResets to its default value the MAXIMUM LINKS value for the localFnode in the volatile database, or removes the MAXIMUM LINKS value fromthe permanent database.3 MAXIMUM_PATH_SPLITSAResets to its default value the MAXIMUM PATH SPLITS value for theGlocal node in the volatile database, or removes the MAXIMUM PATH SPLITS"value from the permanent database.3 MAXIMUM_VISITSBResets to its default value the MAXIMUM VISITS value for the localGnode in the volatile database, or removes the MAXIMUM VISITS value fromthe permanent database.3 NODE;The CLEAR EXECUTOR NODE command clears the default execu torBdesignation. The executor of commands becomes the local node. YouAcannot use the TELL prefix with the CLEAR EXECUTOR NODE command.GAfter you issue the CLEAR EXECUTOR NODE command, NCP on the local node Dperforms all operations using the privileges of your current process=instead of the default nonprivileged or privileged accounts. 3 NONPRIVILEGED itemERemoves from the database the specified nonprivileged access control Dinformation. Specify any or all of the following items for removal: ACCOUNT USER PASSWORD3 OUTGOING_PROXYBResets to its default value the OUTGOING PROXY value for the localBnode in the volatile database, or removes the OUTGOING PROXY valuefrom the permanent database.3 OUTGOING_TIMERBResets to its default value the OUTGOING TIMER value for the localBnode in the volatile database, or removes the OUTGOING TIMER valuefrom the permanent database.3 PATH SPLIT POLICYDResets to its default value the PATH SPLIT POLICY parameter for the >local node in the volatile database, or removes the PATH SPLIT-POLICY parameter from the permanent database.3 PIPELINE QUOTA6Removes the value of PIPELINE QUOTA from the database.3 PRIVILEGED itemBRemoves from the database the specified privileged access control Dinformation. Specify any or all of the following items for removal: ACCOUNT USER PASSWORD3 RETRANSMIT FACTOREResets to its default value the RETRANSMIT FACTOR value for the loca lEnode in the volatile database, or removes the RETRANSMIT FACTOR valuefrom the permanent database.3 ROUTING TIMERGResets to its default value the ROUTING TIMER value for the local node Ein the volatile database, or removes the ROUTING TIMER value from thepermanent database.3 SEGMENT BUFFER SIZEGApplies only to purging the executor. Removes the SEGMENT BUFFER SIZE 5value for the local node from the permanent database.3 STATEBApplies only to purging the executor. Remov!es from the permanent database the local node's state.3 SUBADDRESSES=Removes from the database the value of the range of local DTE subaddresses.3 TYPEFResets to its default value the TYPE of the local node in the volatileCdatabase, or removes the TYPE of the local node from the permanent database. 3 Examples5 NCP>PURGE EXECUTOR IDENTIFICATION INCOMING TIMER> This command removes the local node's identification < string and incoming timer value from th"e permanent  database.% NCP>PURGE EXECUTOR COUNTER TIMER@ This command removes the local node counter timer value% from the permanent database.) NCP>CLEAR EXECUTOR AREA MAXIMUM COST B This command resets to its default value the AREA MAXIMUM1 COST parameter in the volatile database., NCP>SET EXECUTOR NODE TRNTO"GRAY MARY" NCP>CLEAR EXECUTOR NODEB The first command sets the executor node to node TRNTO. #> The second command clears the default executor node ? designation specified previously by the SET EXECUTOR A NODE command. The executor node is now the local node.! 2 LINEHUse the CLEAR LINE command to reset line parameters to the default valueI(if any) or remove the entries and parameters from the volatile database.AFor an X25 line, the default value depends on the profile that is&associated with the NETWORK parameter.+ CLEAR KNOWN LINES $ (parameters...) LINE line-idHUse the PURGE LINE command to remove line parameters from the permanent "database on the local node or DTE.+ PURGE KNOWN LINES (parameters...) LINE line-idFAll underscores found in parameters must be replaced with spaces when $parameters are used in NCP commands. 3 ALLDRemoves the specified line or all known lines from the database. The<line or lines must be in the OFF state before you CLEAR this parameter. 3 %CONTROLLER>Resets to its default the CONTROLLER parameter in the volatileMdatabase, or removes the CONTROLLER value from the permanent database. 3 COUNTER TIMERAResets the logging timer to zero. This prevents any further line*counter logging for the indicated line(s).3 DEAD TIMER BApplies only to DDCMP lines. Resets to its default the DEAD TIMERCparameter in the volatile database, or removes the DEAD TIMER value#from the permanent database. 3 DELAY TIMER &CApplies only to DDCMP lines. Resets to its default the DELAY TIMERDparameter in the volatile database, or removes the DELAY TIMER valuefrom the permanent database. 3 ECHO_DATA@Applies only to FDDI lines. Resets to its default the ECHO DATABparameter in the volatile database. Permanent database operations&cannot be performed on this parameter. 3 ECHO_LENGTHBApplies only to FDDI lines. Resets to its default the ECHO LENGTHBparameter in the volatile database. Permanent database 'operations&cannot be performed on this parameter. 3 ECHO_TARGETBApplies only to FDDI lines. Resets to its default the ECHO TARGETBparameter in the volatile database. Permanent database operations&cannot be performed on this parameter.3 HANGUP=Applies only to asynchronous DDCMP lines. Removes the HANGUPparameter from the database.3 HOLDBACK TIMERFApplies only to X.25 lines. Removes the HOLDBACK TIMER parameter fromDthe database, causing the X.25 software to acknowledge rec(eived data immediately. 3 INTERFACECApplies only to X.25 lines. Resets the INTERFACE parameter to the default value of DTE. 3 KNOWN LINESFResets to the default (if any) or removes the parameters for all knownlines from the database.3 LINE_line-idFIdentifies the specific line whose parameters are to be reset to their5default values (if any) or removed from the database. 3 LINE_SPEEDAApplies only to asynchronous DDCMP lines. Removes the LINE SPEEDparameter from the d)atabase.3 MAXIMUM_BLOCKBApplies only to X.25 lines. Resets the MAXIMUM BLOCK parameter toCthe default value for the specified line or all known lines in the?volatile database, or removes the MAXIMUM BLOCK value from thepermanent database. 3 MAXIMUM_RETRANSMITS9Applies only to X.25 lines. Resets the maximum number ofFretransmissions of a frame to the default value for the specified lineDor all known lines in the volatile database, or removes the MAXIMUM/RETRAN*SMITS value from the permanent database. 3 NETWORKCApplies only to X.25 lines. Removes the NETWORK parameter from thepermanent database. 3 NIF TARGET@Applies only to FDDI lines. Resets to its default value the NIF>TARGET parameter in the volatile database. Permanent database2operations cannot be performed on this parameter. 3 PROTOCOLFApplies to all lines except CI lines. Resets to its default value theDPROTOCOL parameter in the volatile database, or removes the PROTOCOL+Evalue from the permanent database. The line must be in the OFF state before CLEARing this parameter.3 RECEIVE BUFFERS@Resets to its default value the RECEIVE BUFFERS parameter in theDvolatile database, or removes the RECEIVE BUFFERS parameter from theCpermanent database. The line must be in the OFF state in order toCLEAR this parameter.3 REQUESTED TRTGApplies only to FDDI lines. Resets to its default value the REQUESTED DTRT parameter in the volatile database, or remov,es the REQUESTED TRT"value from the permanent database.3 RESTRICTED TOKEN TIMEOUT<Applies only to FDDI lines. Resets to its default value the?RESTRICTED TOKEN TIMEOUT parameter in the volatile database, orBremoves the RESTRICTED TOKEN TIMEOUT parameter from the permanent database.3 RING PURGER ENABLEAApplies only to FDDI lines. Resets to its default value the RINGEPURGER ENABLE parameter in the volatile database, or removes the RING4PURGER ENABLE parameter from the permanent- database.3 SCHEDULING TIMER=Applies only to DDCMP lines. Resets to its default value theCSCHEDULING TIMER parameter in the volatile database, or removes the7SCHEDULING TIMER parameter from the permanent database. 3 SERVICE TIMERFResets SERVICE TIMER to its default value in the volatile database, or<removes the SERVICE TIMER value from the permanent database. 3 SIF_CONFIGURATION_TARGET=Applies only to FDDI lines. Resets to its def .ault value the >SIF CONFIGURATION TARGET parameter in the volatile database. DPermanent database operations cannot be performed on this parameter.3 SIF_OPERATION_TARGET<Applies only to FDDI lines. Resets to its default value the8SIF OPERATION TARGET parameter in the volatile database.DPermanent database operations cannot be performed on this parameter.3 STATEDResets STATE to its default value (OFF) in the volatile database, or4removes the STATE value from the permanent database. / 3 STREAM TIMEREApplies only to DDCMP lines. Resets to its default value the STREAM ETIMER parameter in the volatile database, or removes the STREAM TIMER&parameter from the permanent database.3 SWITCHGApplies only to asynchronous DDCMP lines. Removes the SWITCH parameterfrom the database.3 TRANSMIT PIPELINEFApplies only to DMR11 lines. Removes the TRANSMIT PIPELINE parameter from the database.3 VALID TRANSMISSION TIMEBApplies only to FDDI lines. Res0ets to its default value the VALIDDTRANSMISSION TIME parameter in the volatile database, or removes the>VALID TRANSMISSION TIME parameter from the permanent database. 3 Examples NCP>CLEAR LINE BNA-0 ALLE This command removes the Ethernet line called BNA-0 from the volatile database. NCP>CLEAR LINE DMC-0 ALLA This command removes DDCMP line DMC-0 from the volatile  database.. NCP>CLEAR KNOWN LINES MAXIMUM RETRANSMITSF 1 This command resets the maximum number of retransmissions of E a frame for all known X.25 lines in the volatile database. 5 The parameter is reset to its default value. NCP>CLEAR LINE DMC-* ALLD This command removes all DDCMP DMC lines from the volatile  database.! 2 LOGGINGCUse the CLEAR LOGGING command to remove logging parameters from theFvolatile database on the executor node. Use the PURGE LOGGING commandHto remove logging paramete 2rs from the permanent database on the executornode. CLEAR KNOWN LOGGING ALL+PURGE LOGGING CONSOLE NAME prog-name LOGGING FILE LOGGING MONITORECLEAR KNOWN LOGGING EVENTS event-list CIRCUIT circuit-id ?PURGE LOGGING CONSOLE KNOWN EVENTS LINE line-id > LOGGING FILE NODE node-idA LOGGING MONITOR SINK EXECUTORE 3 NODE node-id@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ALLFIndicates that all logging parameters for the specified component are Eto be removed from the database. The logging component(s) must be inDthe OFF state to use the ALL parameter. The component is no longerrecognized by the network.3 CIRCUIT circuit-idFIdentifies the circuit to which the events apply. Events will not be logged for this 4source. 3 CONSOLECIndicates that the parameters for logging to the console are to be removed from the database.3 EVENTS event-list?Identifies the class and types of events to be removed from the8database. See HELP EVENTS for a list of valid events.  DThe EVENTS event-list parameter may be followed by a specific sourceFfor events (using the CIRCUIT, LINE, or NODE parameters) or a specificAlocation for logging these events (using the SINK parameter). To 5Eremove events associated with a specific source or sink, the specific:source or sink must be specified in the command.  3 FILEFIndicates that the parameters for logging to a file are to be removed from the database.3 KNOWN_EVENTSDIndicates that the event filter is to be removed from the specified "logging component or components. CThe KNOWN EVENTS parameter may be followed by a specific source forCevents (using the CIRCUIT, LINE, or NODE para 6meters) or a specificAlocation for logging these events (using the SINK parameter). ToEremove events associated with a specific source or sink, the specific8source or sink must be specified in the command.  3 KNOWN_LOGGING=Indicates that the specified parameters for all known logging/components are to be removed from the database. 3 LINE line-idBIdentifies the line to which the events apply. Events will not belogged for th7is source. 3 MONITORFIndicates that the parameters for logging to a monitor program are to be removed from the database.3 NAME prog-nameDIndicates that the NAME parameter is to be removed from the databaseCfor the specified component or components. This is the name of theDconsole, file or monitor program. The logging component must be in+the OFF state to CLEAR the NAME parameter. 3 NODE node-idCIdentifies the node to which the events apply. Events will not be logg8ed for this source.3 SINKCIdentifies the node where the event logger runs to log the events. .There are two possibilities:  ENODE node-id Identifies the node at which events are being logged.-EXECUTOR Identifies the executor node.EOnly events being logged to this node are removed from the database. DIf this parameter is omitted, the executor node is assumed to be the7sink node affected.  3 Examples9" NCP>CLEAR LOGGING CONSOLE ALLB This command clears logging to the logging console, afterE which the logging console component is no longer recognized C by the network. The logging console component must be in / the OFF state to perform this command.& NCP>PURGE LOGGING FILE EVENTS 2.*B This command purges logging for all class 2 events to the logging file.4 NCP>SET LOGGING CONSOLE EVENT 4.* CIRCUIT SVA-06 NCP>CLE :AR LOGGING CONSOLE EVENT 4.* CIRCUIT SVA-0D The SET command causes class 4 events for a specific sourceA CIRCUIT SVA-0 to be logged to the logging console. The D CLEAR command stops the logging of class 4 events for that 2 specific source to the logging console. ? Note that since a specific source (CIRCUIT SVA-0) was @ indicated in the SET command, that source must also be C specified in the CLEAR command. That is, a CLEAR LOGGING; @ CONSOLE EVENT 4.* command would not have cleared these 3 events since the source was not specified.# NCP>CLEAR LOGGING MONITOR NAME@ This command removes the name of the monitor program. A The logging monitor must be in the OFF state to perform  this command.: NCP>SET LOGGING CONSOLE KNOWN EVENTS SINK NODE LAMCHP< NCP>CLEAR LOGGING CONSOLE KNOWN EVENTS SINK NODE LAMCHPC The SET command causes all known events generat <ed locally E to be logged to the logging console on remote node LAMCHP. @ The CLEAR command stops the logging of events from the @ local node to the logging console of the remote node. = Note that since a specific location for logging the < events (SINK NODE LAMCHP) was indicated in the SET @ command, that sink must also be specified in the CLEAR A command. In this case, the CLEAR LOGGING CONSOLE KNOWN < EVENTS command wo=uld not have removed these events , because the SINK was not specified.!  2 MODULE 'Introduces the various module entities.3 CONFIGURATORAUse CLEAR MODULE CONFIGURATOR command to remove from the volatileGdatabase the Ethernet module configurator parameters for all circuits. @The CLEAR command can not be used to remove individual circuits.7 BUse PURGE MODULE CONFIGURATOR command to remove from the permanentFdatabase> the Ethernet module configurator parameters for the specifiedcircuit or circuits.The word MODULE is optional.< CLEAR MODULE CONFIGURATOR KNOWN CIRCUITS ALL< PURGE MODULE CONFIGURATOR KNOWN CIRCUITS ALL< CIRCUIT circuit-id ALL 4 Examples5 NCP>PURGE MODULE CONFIGURATOR KNOWN CIRCUITS ALLA This command removes from the permanent database at the B local node all configurator module parameters r?elated to % all known Ethernet circuits.4 NCP>PURGE MODULE CONFIGURATOR CIRCUIT SVA-0 ALLA This command removes from the permanent database at the B local node all configurator module parameters related to  the SVA-0 circuit.5 NCP>CLEAR MODULE CONFIGURATOR KNOWN CIRCUITS ALL= This command removes from the volatile database all = configurator module parameters related to all known  Ethernet circuits. @ 3 X25-ACCESS CUse the CLEAR MODULE X25-ACCESS command to remove from the volatileEdatabase network names and parameters used by the host node to accessIa specified X.25 network or networks through a connector node. DUse the PURGE MODULE X25-ACCESS command to remove these same networkDnames and parameters from the permanent database. ? CLEAR MODULE X25-ACCESS NETWORK net-name ACCOUNT; PURGE KNOWN NETWORKAS ALL@ PASSWORD< USER@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 4 ACCOUNT DRemoves the account access control information from the database forEthe specified network or all known networks. 4 ALL =Removes all parameters for the specified network or all knownnetworks in the dataBbase. 4 KNOWN NETWORKS Identifies all known networks. 4 NETWORK net-name >Identifies the network whose parameters are to be removed fromthe database. 4 PASSWORD ERemoves the password access control information from the database forFthe specified network or all known networks. 4 USER CRemoves the user identification from the database for the specifiednetwork or all known networks. 4 Examples6 NCP>CLEAR MODULE X25-ACCESS NETWORK TELECNET1 ALL= This command removes the network TELENET1 from the ? volatile database in the local node. The local node = can no longer connect to the X.25 network TELENET1 % through the connector node.; NCP>CLEAR MODULE X25-ACCESS NETWORK TELENET1 PASSWORD; This command removes the password access control 8 information for the network TELENET1 from the . volatile database in the local node.! 3 X25-PROTOCOLA DUse the CLEAR MODULE X25-PROTOCOL command to remove the protocolCmodule component from the volatile database or reset the individual?parameters. (Parameters are reset to their default values; theAnetwork values are specified by the PROFILE parameter of the SET MODULE X25-PROTOCOL command.) FUse the PURGE MODULE X25-PROTOCOL command to remove the parameters ofFthe protocol module component from the permanent database. Note thatthe word MODULE is optional. EUse separate E CLEAR or PURGE MODULE X25-PROTOCOL commands to clear or Apurge the network, the DTE, or the group. You may not be able toCchange the values of some of the network parameters (see the Public*Network Information manual).  CCLEAR MOD X25-PROTOCOL DTE dte-addr NETWORK net-name dte-param(s)3PURGE KNOWN DTES KNOWN NETWORKS+CLEAR MOD X25-PROTOCOL GROUP group-name ALL'PURGE KNOWN GROUPS ALL+CLEAR MOD X25-PROTOCOL NETWORK net-namFe ALL)PURGE KNOWN NETWORKS ALL@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 4 DTE_dte-addr?Removes parameters for the specified DTE. The DTE address is a-decimal integer of 1 to 15 digits. @CLEAR MOD X25-PROTOCOL DTE dte-addr NET net-name dte-param(s)3PURGE KNOWN DTES KNOWN NETWORKSDThe NETWORK or KNOWN NETWORKS parameter is required to identify the Enetwork or netGworks to which the DTE belongs. You must also include Aone or more of the following dte parameters. 5 ALL,Removes the specified DTE from the database. 5 CALL TIMER <If used with the CLEAR command, resets the call timer in the?volatile database to its default value. If used with the PURGE?command, resets the call timer in the permanent database to 0. ?This means that the call request will not time out at the local(DTE, but may be cleared by the network. # H 5 CLEAR TIMER =If used with the CLEAR command, resets the clear timer in the?volatile database to its default value. If used with the PURGE<command, resets the clear timer in the permanent database toDprevent retransmission of a request to clear a virtual circuit. % 5 COUNTER TIMER 8Resets the counter timer to its default in the volatile @database, or removes the COUNTER TIMER value from the permanent databaIse. 5 DEFAULT_DATA :Resets the default packet size to its default value in the=volatile database, or removes the DEFAULT DATA value from thepermanent database.5 DEFAULT_WINDOW :Resets the default window size to its default value in the?volatile database, or removes the DEFAULT WINDOW value from thepermanent database.3 5 INTERRUPT TIMER ?Resets the INTERRUPT TIMER to its default value in the volatileAdatabase, or removJes the INTERRUPT TIMER value from the permanent database.5 MAXIMUM_CIRCUITS @Resets the maximum number of virtual circuits allowed at once onAthe DTE to its default value in the volatile database, or removes7the MAXIMUM CIRCUITS value from the permanent database.5 MAXIMUM_CLEARS ?Resets the maximum number of attempts to clear a circuit to the>default value in the volatile database, or removes the MAXIMUM)CLEARS value from the permanent database.4 K 5 MAXIMUM_DATA :Resets the maximum packet size to its default value in the=volatile database, or removes the MAXIMUM DATA value from thepermanent database.2 5 MAXIMUM_RESETS ?Resets to its default value the MAXIMUM RESETS parameter in the?volatile database, or removes the MAXIMUM RESETS value from thepermanent database.1 5 MAXIMUM_RESTARTS AResets to Lits default value the MAXIMUM RESTARTS parameter in theAvolatile database, or removes the MAXIMUM RESTARTS value from thepermanent database./ 5 MAXIMUM_WINDOW:Resets the maximum window size to its default value in the?volatile database, or removes the MAXIMUM WINDOW value from thepermanent database.0 5 RESET TIMER <Resets to its default value the RESET TIMER parameter in the<volatile dMatabase, or removes the RESET TIMER value from the9permanent database to prevent retransmission of a reset. 5 RESTART TIMER >Resets to its default value the RESTART TIMER parameter in the>volatile database, or removes the RESTART TIMER value from theDpermanent database to prevent retransmission of a restart. 4 GROUP_group-name?Removes parameters for the specified closed user group (CUG) or?bilateral closed user group (BCUG) from the database. The ALLparameter is mandaNtory.- 4 KNOWN_DTES <Selects all known DTEs on the network specified or all known networks. @CLEAR MOD X25-PROTOCOL DTE dte-addr NETWORK net-name dte-params2PURGE KNOWN DTES KNOWN NETWORKS?The NETWORK or KNOWN NETWORKS parameter is required to identifyAthe network or networks to which the DTEs belong. You must also7include one or more of the following dte parameters.  5 ALL9Removes all known DTEs fOor the specified network or knownnetworks from the database. 5 CALL TIMER <If used with the CLEAR command, resets the call timer in the?volatile database to its default value. If used with the PURGE?command, resets the call timer in the permanent database to 0. ?This means that the call request will not time out at the local(DTE, but may be cleared by the network. 5 CLEAR TIMER =If used with the CLEAR command, resets the clear timer in the?volatile database to its default vPalue. If used with the PURGE<command, resets the clear timer in the permanent database to@prevent retransmission of a request to clear a virtual circuit. 5 COUNTER TIMER @Resets the counter timer to in the volatile database, or removes0the COUNTER TIMER from the permanent database. 5 DEFAULT_DATA:Resets the default packet size to its default value in the=volatile database, or removes the DEFAULT DATA value from thepermanent database.5 DEFAULT_WINDOW :Resets the defaultQ window size to its default value in the?volatile database, or removes the DEFAULT WINDOW value from thepermanent database.5 INTERRUPT TIMER?Resets the INTERRUPT TIMER to its default value in the volatileAdatabase, or removes the INTERRUPT TIMER value from the permanent database.5 MAXIMUM_CIRCUITS@Resets the maximum number of virtual circuits allowed at once onAthe DTE to its default value in the volatile database, or removes7the MAXIMUM CIRCUITS value from the permanent daRtabase.5 MAXIMUM_CLEARS ?Resets the maximum number of attempts to clear a circuit to the>default value in the volatile database, or removes the MAXIMUMACLEARS value from the permanent database. 5 MAXIMUM_DATA:Resets the maximum packet size to its default value in the=volatile database, or removes the MAXIMUM DATA value from thepermanent database.. 5 MAXIMUM_RESETS?Resets to its default value the MAXIMUM SRESETS parameter in the?volatile database, or removes the MAXIMUM RESETS value from thepermanent database.5 MAXIMUM_RESTARTS AResets to its default value the MAXIMUM RESTARTS parameter in theAvolatile database, or removes the MAXIMUM RESTARTS value from thepermanent database.- 5 MAXIMUM_WINDOW:Resets the maximum window size to its default value in the?volatile database, or removes the MAXIMUM WINDOW value from thepermanent dataTbase.5 RESET TIMER <Resets to its default value the RESET TIMER parameter in the<volatile database, or removes the RESET TIMER value from the9permanent database to prevent retransmission of a reset. , 5 RESTART TIMER >Resets to its default value the RESTART TIMER parameter in the>volatile database, or removes the RESTART TIMER value from the;permanent database to prevent retransmission of a restart.  4 KNOWN_GROUPS @RemoveUs parameters of all known groups in the database. The ALLparameter is mandatory.4 KNOWN_NETWORKS >Removes parameters of all known networks in the database. TheALL parameter is mandatory. 4 NETWORK net-name:Removes all DTEs, groups, and parameters for the specified;network from the database. The ALL parameter is mandatory. 4 Examples3 NCP>CLEAR MODULE X25-PROTOCOL GROUP ESECUG ALL@ This command removes the closed user group ESECUG from  the vVolatile database.3 NCP>PURGE MODULE X25-PROTOCOL GROUP ESECUG ALL@ This command removes the parameters of the closed user = group ESECUG from the permanent database. When the < system is rebooted, the group no longer exists for  VAX P.S.I.2 NCP>CLEAR MODULE X25-PROTOCOL DTE 123789456 - _ NETWORK PSS1 ALL= This command removes the specified DTE belonging to 5 the network PSS1 from the volatile database.2 NCP>P WURGE MODULE X25-PROTOCOL DTE 123789456 - _ KNOWN NETWORKS ALL@ This command removes all parameter entries for all the @ DTEs of that DTE number, for all networks in which the < DTE exists, from the permanent database. When the < network is restarted, the DTE no longer exists for  VAX P.S.I.& NCP>CLEAR MODULE X25-PROTOCOL ALL: This command removes all network, DTE, group and : X25-PROTOCOL module parameters from the volXatile  database.3 NCP>CLEAR MODULE X25-PROTOCOL NETWORK PSS1 ALL= This command removes all DTEs and groups on network < PSS1 and then removes the network name itself from  the volatile database.> NCP>CLEAR MODULE X25-PROTOCOL KNOWN DTES KNOWN NETWORKS - _ COUNTER TIMER > This command removes the COUNTER TIMER parameter for = all DTEs on all networks from the volatile database.!  3 X25-SERVER FUse the CLEAYR MODULE X25-SERVER or CLEAR MODULE X29-SERVER command to Ereset or remove the parameters of the X.25 Call Handler or X.29 Call "Handler in the volatile database. FUse the PURGE MODULE X25-SERVER or PURGE MODULE X29-SERVER command to Cremove the parameters of the X.25 Call Handler or X.29 Call Handlerfrom the permanent database. The word MODULE is optional.)CLEAR MODULE X25-SERVER COUNTER TIMERPURGE X29-SERVER ?CLEAR MODULE X25-SERVER DESTINATION destZ-name dest-params 5PURGE X29-SERVER KNOWN DESTINATIONS @All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 4 COUNTER TIMER AResets the module counter timer to zero in the volatile database,?or removes the COUNTER TIMER value from the permanent database. 4 DESTINATION_dest-name >Identifies the destination whose parameters are to be reset or@removed from the database. [  @CLEAR MODULE X25-SERVER DESTINATION dest-name dest-params !PURGE X29-SERVER <The destination-params include one or more of the following: 5 ACCOUNT 7Removes the account from the database for the specified destination.5 ALL =Removes all parameters for the specified destination from the database. 5 CALL_MASK 9Removes the call mask from the database for the specified destination. 5 CALL_VALUE :Removes the call value from the da\tabase for the specified destination.5 CALLED ADDRESS8Removes from the database the called DTE address for thespecified destination. 5 EXTENSION_MASK>Removes from the database the extension mask for the specified destination.5 EXTENSION_VALUE?Removes from the database the extension value for the specified destination.5 GROUP :Removes the group name from the database for the specified destination. 5 INCOMING ADDRESS@Removes from t]he database the incoming address for the specified destination. 5 NETWORK<Removes from the database the network name for the specified destination.5 OBJECT;Removes from the database the object identification for thespecified destination. 5 PASSWORD 8Removes the password from the database for the specified destination. 5 PRIORITY 9Resets the priority to the lowest value for the specified=destination in the volatile database, or removes the PRIORITYAvalue for the sp^ecified destination from the permanent database. 5 RECEIVING DTE;Removes from the database the receiving DTE address for thespecified destination.5 REDIRECT REASON:Removes from the database the redirect reason code for thespecified destination.5 SENDING ADDRESS9Removes from the database the sending DTE address for thespecified destination.5 SUBADDRESSES @Removes the subaddress range from the database for the specified destination.5 USER 9Removes _the user identification from the database for thespecified destination.4 KNOWN_DESTINATIONS <Identifies all known destinations whose parameters are to be=reset or removed from the database.  <CLEAR MODULE X25-SERVER KNOWN DESTINATIONS dest-params PURGE X29-SERVER 5The dest-params include one or more of the following. 5 ACCOUNT BRemoves the account from the database for all known destinations. 5 ALL 8Removes all parame`ters for all known destinations in the database. 5 CALL_MASK 5Removes the call mask from the database for all knowndestinations. 5 CALL_VALUE 6Removes the call value from the database for all knowndestinations. 5 CALLED ADDRESS>Removes from the database the called DTE address for all known destinations. 5 EXTENSION_MASK:Removes from the database the extension mask for all known destinations. 5 EXTENSION_VALUE;Removes from the database the exatension value for all known destinations. 5 GROUP 6Removes the group name from the database for all knowndestinations.  5 INCOMING ADDRESS<Removes from the database the incoming address for all known destinations. 5 NETWORK8Removes from the database the network name for all known destinations.5 OBJECTBRemoves from the database the object identification for all known +destinations. 5 PASSWORD 4Removes bthe password from the database for all knowndestinations. 5 PRIORITY 5Resets the priority to the lowest value for all known?destinations in the volatile database, or removes the PRIORITY?value for all known destinations from the permanent database.  5 RECEIVING DTEARemoves from the database the receiving DTE address for all known destinations. 5 REDIRECT REASON@Removes from the database the redirect reason code for all known destinations. c 5 SENDING ADDRESS@Removes from the database the sending DTE address for all known destinations.5 SUBADDRESSES =Removes the subaddress range from the database for all known destinations. 5 USER @Removes the user identification from the database for all known destinations. !  4 Examples7 NCP>CLEAR MODULE X25-SERVER KNOWN DESTINATIONS ALL= This command removes all X.25 destinations from the  volatile database.7 NCP>PURGE MdODULE X25-SERVER KNOWN DESTINATIONS ALL= This command removes all X.25 destinations from the  permanent database. 3 X29-SERVERFUse the CLEAR MODULE X29-SERVER or CLEAR MODULE X25-SERVER command to Ereset or remove the parameters of the X.29 Call Handler or X.25 Call "Handler in the volatile database. FUse the PURGE MODULE X29-SERVER or PURGE MODULE X25-SERVER command to Cremove the parameters of the X.29 Call Handler or X.25 Call Handlerfrom the permanent dateabase. The word MODULE is optional.)CLEAR MODULE X25-SERVER COUNTER TIMERPURGE X29-SERVER >CLEAR MODULE X25-SERVER DESTINATION dest-name dest-params5PURGE X29-SERVER KNOWN DESTINATIONS AFor additional help see the CLEAR MODULE X25-SERVER command which?is identical in format to the CLEAR MODULE X29-SERVER command. ! 2 NODEFUse the CLEAR NODE command to remove node parameters from the volatileHdatabase. Use the PURGE NODE command to rfemove node parameters from thepermanent database.FTo remove a loop node name from the database, use the CLEAR/PURGE NODEHnode-id command and specify either the ALL parameter (with the loop node:name or address as the node-id), or the CIRCUIT parameter.5 (CLEAR KNOWN NODES (parameters ...)PURGE NODE node-id@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ACCESSgDRemoves the ACCESS value from the database for the specified node orall known nodes.: 3 ALLERemoves all parameters for the specified node or all known nodes fromDthe database. The component is no longer recognized by the network. 3 CIRCUITBRemoves a loop node parameter associated with the circuit from the database.9 3 COUNTER TIMER2Removes the counter timer vahlue from the database.3 CPU9Removes the node's CPU identification from the database. 3 DIAGNOSTIC FILE<Removes from the database the identification of the downlineloading diagnostics file.3 DUMP_ADDRESS>Removes the up-line dump address of the adjacent node from the database. 3 DUMP_COUNT1Removes the up-line dump count from the database. 3 DUMP_FILE@Removes the up-line dump file identification from the database. 3 HARDWARE ADDRESSFRemoves from the database the hardiware address that is associated withthe node's LAN controller.3 HOST>Removes the identification of the host node from the database. 3 INBOUNDGApplies only to nodes on dynamic asynchronous DDCMP circuits. Removes (the INBOUND parameter from the database.2 3 KNOWN NODES;Indicates that the specified parameters for all known nodes$are to be removed from the database.3 LOAD_ASSIST_AGENTFRemoves from the database the identifica jtion of the OpenVMS image usedFto assist a downline load. The LOAD ASSIST AGENT parameter applies to=downline load operations to Local Area Cluster members only.: 3 LOAD_ASSIST_PARAMETERFRemoves from the database the identification of the value to be passedEto the load assist agent. The LOAD ASSIST PARAMETER value applies to=downline load operations to Local Area Cluster members only.9 k 3 LOAD_FILE>Removes from the database the identification of the file to bedownline loaded.3 MANAGEMENT FILEERemoves from the volatile the identification of the downline loading management information file.3 NAME?Removes from the database the node name parameter for the node.3 NODE node-id@Identifies the node (local or remote) whose parameters are to beCremoved from the database. 3 NONPRIVILEGED itemCRemovels the specified nonprivileged access control information fromEthe database. Specify any or all of the following items for removal: ACCOUNT PASSWORD USER 3 PRIVILEGED itemDRemoves the specified privileged access control information from theAdatabase. Specify any or all of the following items for removal: ACCOUNT PASSWORD USER 3 RECEIVE PASSWORDDRemoves the receive password expected from the remote node during a 2Routing initialization sequence mfrom the database.3 SECONDARY LOADERBRemoves the identification of the secondary downline loading file from the database.3 SERVICE_CIRCUITDRemoves the circuit parameter associated with the node for downline #loading purposes from the database.3 SERVICE_DEVICEGRemoves the service device type from the database. See HELP PARAMETERS'DEVICE-TYPE for a list of device types.<Only the synchronous port on the DMF may be used for service operations.3 SERVICE_NODE_VERSIONBnRemoves the service node version number of the node to be downlineloaded from the database.3 SERVICE_PASSWORDDRemoves from the database the password parameter required to trigger:the bootstrap mechanism of the node to be downline loaded.3 SOFTWARE_IDENTIFICATION=Removes the identification of the software from the database.3 SOFTWARE_TYPEARemoves the initial load software program type from the database.3 TERTIARY LOADERERemoves the identification of the tertiary downline oloading file from the database.3 TRANSMIT PASSWORDBRemoves from the database the transmit password sent to the remote.node during a Routing initialization sequence. 3 Examples NCP>CLEAR NODE TRNTO ALLE This command removes all parameter entries for node TRNTO in@ the volatile database. As a result, the node no longer; exists in the volatile database of the local node. NCP>CLEAR NODE 14 NAME NCP>SET NODE 15 NAME DENVERD T phe first command disassociates the name (which happens to C be DENVER) from node 1.14. The second command associates C the same name with node 1.15. Note that the default area A number 1 is assumed if your network is not divided into  multiple areas.  NCP>CLEAR NODE 5.14 NAME" NCP>SET NODE 5.15 NAME DENVERD The first command disassociates the name (which happens to C be DENVER) from node 5.14. The second command associates qB the same name with node 5.15. Use this example in place B of the previous example when the network is divided into  multiple areas.+ NCP>CLEAR NODE BOSTON RECEIVE PASSWORDB This command removes node BOSTON's receive password from 1 the volatile database of the local node. NCP>CLEAR NODE 5.* NAME> This command disassociates the node names from their + addresses for all nodes in area 5.& NCP>SET NODE TESTER CrIRCUIT FZA-0" NCP>CLEAR NODE TESTER CIRCUIT@ The first command sets a loop node for circuit FZA-0. ; The second command removes the loop node from the  volatile database.! 2 OBJECTAUse the CLEAR OBJECT command to remove object parameters from theBvolatile database. Use the PURGE OBJECT command to remove object 'parameters from the permanent database.-CLEAR KNOWN OBJECTS (parameters...)PURGE OBJECT object-name@All underscores founsd in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ACCOUNTARemoves from the database the account access control information.3 ALIAS_INCOMING>Removes from the database the ALIAS INCOMING parameter for theDspecified object or all known objects. Does not apply to VAX P.S.I.3 ALIAS_OUTGOING>Removes from the database the ALIAS OUTGOING parameter for theMspecified object or all known objects. Does not apply to VAX P.S.I. 8 t 3 ALLCIndicates that all parameters for the specified object or all knownBobjects 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 database.3 KNOWN OBJECTSDIndicates that the specified parameters for all known objects are tobe removed from the database.3 OBJECT object-nameBIdentiufies the object whose specified parameters are to be removedfrom the database.3 OUTGOING CONNECT PRIVILEGESERemoves the privileges required to make an outbound connection to the$object. Does not apply to VAX P.S.I.6 3 PASSWORDBRemoves the password access control information from the database. 3 PRIVILEGES=Removes the privileges required to access the object from the&database. Does not apply to VAX P.S.I.3 PROXYDRemovves the proxy access control information for the object from the-database. Does not apply to VAX P.S.I. 3 USER>Removes the user access control information from the database. 3 Examples NCP>CLEAR OBJECT DTR ALL@ This command removes all parameter entries for the DTR C object in the volatile database. As a result, the object D no longer exists for the local DECnet for OpenVMS software.! ww7כ , 1 CommandsBThe command syntax w has four parts: a command keyword, a component@keyword(s), one or more parameters, and, optionally, one or more&qualifiers. The command keywords are:;SET Change parameters in the volatile database.<DEFINE Change parameters in the permanent database.8CLEAR Remove components or parameters from the2PURGE volatile or permanent databases.;SHOW Display information about components in the2LIST volatile or permanent databases.8 xDISCONNECT Disconnect logical links with processes.2COPY Copy one node database to another.3LOOP Test lines or connections to nodes.$LOAD Downline load nodes.6TRIGGER Initiate bootstrap sequence of a node.2TELL Establish temporary executor node.7ZERO Zero counters for the specified entity.>CONNECT Connect local terminal to remote node console  interface.@All underscores found in parameters must bye replaced with spaces)when parameters are used in NCP commands. 2 SyntaxBThe command syntax has four parts: a command keyword, a componentAkeyword(s), one or more parameters, and, optionally, one or morequalifiers. For example,C Command Keyword Component Parameter QualifierD SHOW ACTIVE CIRCUITS CHARACTERISTICS TO file-id1 KNOWN CIRCUITS COUNTERS/ CIRCUIT line-id STATUS0 z SUMMARYAFor each command, you must supply a keyword, a component, and one<or more parameters from the parameter list. In general, theDorder in which you specify parameters makes no difference. Braces Daround keywords and parameters indicate that you must choose one of Ethe options. Lowercase letters indicate user-supplied component and parameter values.2 Issuing_commandsEYou enter NCP commands as keywords and parameters separated by spacesDor tabs. { Use the standard continuation line convention--a hyphen asFthe last character in the line--to continue a long command to the nextDline. If the first character of a line is an exclamation point (!),Dthe line is ignored by NCP as a comment line. Hyphens within and at?the end of a comment line are ignored. Lines beginning with anDexclamation point, however, are not ignored if they follow a commandline ending with a hyphen.BWhen entering an NCP command, you can abbreviate any command verb,|Bcomponent keyword, or parameter name to its fewest unique letters.wwW , 1 CONNECTAUse the CONNECT command to enable a local terminal to act as the console for a remote system.2 NODEDUse the CONNECT NODE command to set up a logical connection between Dthe host node and the console interface on a specified target node. DBoth the host node and the target node must be on the same broadcast circuit. CTo define information for the target node in the volatile data}base,Euse the NCP command SET NODE to specify the ADDRESS, SERVICE CIRCUIT,ASERVICE PASSWORD, and HARDWARE ADDRESS parameters for the target>node. Once you set these parameters, you can override them by5specifying new parameters in the CONNECT command.  (CONNECT NODE node-id (parameters ...)@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 PHYSICAL ADDRESS p-addressDSpecifies the physical address of the ~target node. The value is theCphysical address that the target node has set for itself or, if the@target node has not set a physical address, the hardware address4associated with the target node's device controller.> 3 SERVICE PASSWORD hex-passwordCIdentifies the password required to create the logical link between>the host node and the target node. The password is a 16-digit6hexadecimal number in the range 0 to FFFFFFFFFFFFFFFF.3 VIA circuit-idDSpecifies the circuit to be used to create the logical link between Dthe host node and the target node. This circuit must be a broadcast circuit. 3 Examples@ NCP>CONNECT NODE RTRDEV SERVICE PASSWORD FEFEFEFEFEFEFEFE -3 _ VIA UNA-0 PHYSICAL ADDRESS AA-00-04-00-38-04< This command connects the host node to the console < interface on the target node RTRDEV specifying the @ service password FEFEFEFEFEFEFEFE, the service circuit ; UNA-0, and the physical address AA-00-04-00-38-04. NCP>CONNECT NODE RTRDEV= Since the physical address is not specified in this > command, the host node acquires the hardware address 9 associated with node RTRDEV from its local node @ database, and then attempts to connect using a channel $ to that hardware address. > If the connection attempt using the hardware address > channel is unsuccessful, the ho st node uses the node ? address associated with node RTRDEV in its local node = database to construct a physical address. The host : node will then attempt to connect using a channel$ to that physical address. ? NCP>CONNECT NODE RTRDEV PHYSICAL ADDRESS 08-00-2B-22-45-CD? The host will connect to the target node RTRDEV using : a channel to the address 08-00-2B-22-45-CD. The @ address specified in the command overrides the de fault ? node information provided by the host node's volatile  node database.2 VIACUse the CONNECT VIA command to set up a logical connection between Bthe host node and the console interface on a target node using theDspecified circuit. If the DECnet node address of the target node isBnot known, use the CONNECT VIA command instead of the CONNECT NODECcommand. Both the host node and the target node must be on the samebroadcast circuit.=  =CONNECT VIA circuit-id PHYSICAL ADDRESS p-address (parameter)3 PHYSICAL ADDRESS p-addressDSpecifies the physical address of the target node. The value is theCphysical address that the target node has set for itself or, if the@target node has not set a physical address, the hardware addressDassociated with the target node's device controller. This parameter is required.3 SERVICE PASSWORD hex-passwordCIdentifies the password required to create the logical link between>the host node and the target node. The password is a 16-digit7hexadecimal number in the range 0 to FFFFFFFFFFFFFFFF. 3 Examples= NCP>CONNECT VIA UNA-0 PHYSICAL ADDRESS 08-00-2B-22-45-CDE This command connects the host node to the console interfaceD on the target node by specifying the circuit over which theE connection is to be made and the physical address currently # in use by the target node.! wwh ,1 COPYCThe COPY KNOWN NODES command updates the node database on the localDnode. You can copy the volatile or permanent database from a remoteCnode to either or both the volatile and permanent databases on the Elocal node. You also have the option of clearing or purging the nodeBdatabase on the local node before the copy operation is performed.EOnly the node name and address are copied. A node entry will not be Ecopied into the node database if a node with the same name or addressalready exists in the database.AYou cannot use the TELL prefix with the COPY KNOWN NODES command./ COPY KNOWN NODES FROM node-id USING 2 TO4 WITH 2 KNOWN NODESAKNOWN NODES indicates that names and addresses of all known nodesLstored in the database of the specified remote node are to be copied. > 2 FROM node-id@Specifies the remote node from which the copy is to be made. TheEremote node can be any node in the network to which you have access. The word FROM is optional.= 2 USING option=Specifies the node database on the remote node from which the<information 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. 2 TO optionFSpecifies the node database on the local node to which the information1is 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. 2 WITH optionCClears or purges the node database on the local node beforethe copyFoperation is performed. Retains the executor node characteristics and;the name and address of the remote node from which the node@information is to be copied. The node database to be cleared orFpurged is the local database to which the information will be copied. BThe node database to be cleared or purged is the local database to=which the information will be copied. There are two options:: CLEAR Clears the volatile database at the local node.@ PURGE Purges the permanent node database at the local node.CNote that you can specify CLEAR or PURGE for either database or forboth databases.EIf you do not specify the WITH qualifier, the node entries copied are7added to the existing node database(s). 2 Examples4 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-NMLR SP, 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 permanentE node database on the local node (ROBIN). The node database 6 is purged before the copy operation is begun.# NCP>COPY KNOWN NODES FROM LARK? This COPY command copies the node information from the> volatile node database on node LARK into the volatileC node database on the local node (ROBIN). In this example,D the volatile node database on the local node is not cleared, before the copy operation is begun.! ww@ ,1 DEFINEFUse the DEFINE command to create or modify parameters or components inAthe permanent database on the executor node. See the SET command4description for the format and allowable parameters.! wwh , 1 DISCONNECTDUse the DISCONNECT command to disconnect logical links active on theexecutor node.8 DISCONNECT KNOWN LINKS WITH NODE node-id" LINK number 2 KNOWN LINKS0Indicates that all links are to be disconnected. 2 LINK numberCIdentifies the particular logical link to be disconnected. Use theDSHOW KNOWN LINKS command to display the active logical links for the local node.: 2 WITH NODE node-id:Identifies the node with which all logical links are to beCdisconnected. The node-id is either a node name or a node address. FYou can use this command verb only with the KNOWN LINKS component, not9the LINK number component. ; 2 Examples NCP>DISCONNECT LINK 1840, This command disconnects link 1840./ NCP>DISCONNECT KNOWN LINKS WITH NODE TRNTOG This command disconne cts all known links to remote node TRNTO.! NCP>SET EXECUTOR NODE DENVER NCP>DISCONNECT KNOWN LINKS NCP>CLEAR EXECUTOR NODEB The first command sets the executor node to DENVER. The E DISCONNECT KNOWN LINKS command disconnects the all DENVER's A known links, including links from the local node to the H executor. As a result, you must either enter the SET EXECUTOR G NODE command again, or you must enter the CLEAR EXECUTOR NODE D  command to reestablish the local node as the executor node.! ww? ,1 EVENTSCThe following is the list of events that can be reported with eventAlogging. Not all events are generated by DECnet, but if a DECnetCsystem acts as a sink node for another system, it may report any of these events.0.0 Event records lost0.1 Automatic node counters0.2 Automatic line counters0.3 Automatic line service0.4 Line counters zeroed0.5 Node counters zeroed0.6 Passive loopback0.7 Aborted service request0.8 Automatic counters0.9 Counters zeroed2.0 Local node state change2.1 Access control failure3.0 Invalid message3.1 Invalid flow control3.2 Data base reused!4.1 Node unreachable packet loss"4.2 Node out-of-range packet loss4.3 Oversized packet loss4.4 Packet format error 4.5 Partial routing update loss4.6 Verification reject 4.7 Circuit down, circuit fault4.8 Circuit down&4.9 Circuit down, operator initiated 4.10 Circuit up4.11 Init failure, line fault4.12 Init failure%4.13 Init failure, operator initiated4.14 Node reachability change4.15 Adjacency up4.16 Adjacency rejected 4.17 Area reachability change4.18 Adjacency down'4.19 Adjacency down, operator initiated"5.0 Locally initiated state change#5.1 Remotely initiated state change15.2 Protocol restart received in maintenance mode5.3 Send error threshold5.4 Receive error threshold5.5 Select error threshold5.6 Block header format error5.7 Selection address error5.8 Streaming tributary5.9 Local buffer to small5.13 Line initialization error5.14 Send failure on line5.15 Receive failed on line*5.16 Collision detect check failed on line 5.17 DTE up 5.18 DTE down 5.19 Retransmit maximum exceeded5.20 FRMR received5.21 Illegal frame received7.0 DTE state change7.1 Illegal packet received7.2 Invalid LCN7.3 Flow control invalid 7.4 Restart 7.5 Clear 7.6 Reset7.7 Diagnostic 7.8 Reject#7.9 Retransmission maximum exceeded7.10 Call failed7.11 State change 128.1 DAP CRC error detected%128.2 Duplicate Phase 2 address error128.3 Process created128.4 Process terminated! ww7כ ,1 EXIT8To exit NCP, enter EXIT or CTRL/Z after the NCP> prompt.wwP ,1 HELPIThe Network Control Program (NCP) is the utility program system managers Hand operators use to configure and control DECnet for OpenVM S networks. GSystem managers can also use NCP to monitor network resources and test network components. JUse the HELP command to display information at various levels of detail. IFor example, each HELP display includes a list of command words under an I"Additional Information Available" section. These command words serve as Itopics for the next level of information accessible by the HELP command. FIn the general format of the HELP command shown below, the topic is a command word from the list: NCP>HELP [topic...]FYou can abbreviate command words when you issue the command. Once you Benter a particular level of detail, that level becomes the currentHlevel for accessing information. Through the use of the prompts "TOPIC?"Iand "SUBTOPIC?" you can return to a higher or lower level of information,=respectively. The highest level of information is the general!description of the help facility. 2 Parameters topic...A Specifies one or more topics that indicate what information youC want. Information is located in a hierarchical manner, depending' on the level of information required.A If you specify an asterisk (*) in place of any topic, the HELP; command displays all information available at that level.? If you specify an ellipsis (...) after any topic, you obtain, everything in the help file at that level.B You can specify percent signs (%) and asterisks (*) in the topic as wild card characters.! ww@ ,1 LISTGUse the LIST command to display information from the permanent databaseFon the executor node. See the SHOW command description for the format-and possible parameters for the LIST command.! ww ,1 LOAD@Use the LOAD command to downline load software to a target node.2 NODEDUse the LOAD NODE command to downline loadsoftware to a target node,Ausing either the identified circuit (if specified) or the circuitDobtained from the volatile database. Any parameter left unspecified@in the command defaults to whatever entry for the target node isRspecified in the volatile node database on the executor node.  (LOAD NODE node-id (parameters ...)@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ADDRESS node-addressDIdentifies the address that the target node is to use (when it comesup). C3 CPU  5Identifies the target node's CPU type. There are fourpossibilities: DECSYSTEM1020 PDP11 PDP8 VAX3 FROM file-specAIdentifies the file specification of the load file containing the'system software to be downline loaded.3 HOST node-idDIdentifies the default host that the target node is to use (when it comes up).3 LOAD_ASSIST_AGENT file-specFSpecifies the OpenVMS image that will de fine the system software to beFdownline loaded to the target node. The load assist agent can be usedBto tailor the system software to be loaded. The LOAD ASSIST AGENT<parameter applies to downline load operations for Local AreaVAXclusters only.3 LOAD_ASSIST_PARAMETER itemDSpecifies a parameter to be passed to a load assist agent. The LOADCASSIST PARAMETER value applies to downline load operations to Local;Area VAXclusters only. 3 MANAGEMENT FIL E file-spec?Specifies a file containing management information for downlineloading to the target node. 3 NAME node-nameFIdentifies the name that the target node is to use (when it comes up).3 PHYSICAL ADDRESS p-addressCApplies only to broadcast circuits. Specifies the address that theEtarget node to be downline loaded currently uses to identify itself. BThe value is the physical address that the target node has set forAitself or, if the target node has not se t a physical address, theEhardware address associated with the target node's device controller. 3 SECONDARY LOADER file-specEIdentifies the file specification of a secondary loader program which%performs the downline load operation.) 3 SERVICE_DEVICE device-typeFIdentifies the target node's line controller for the service line overFwhich the operation is to take place. See HELP PARAMETERS DEVICE-TYPEfor a list of devices. ( COnly the synchronous port on the DMF service device may be used forservice operations.  3 SERVICE_PASSWORD hex-passwordFIdentifies the password required to trigger the bootstrap mechanism onBthe target node. The password is a hexadecimal number. For DDCMP=circuits, it is in the range of 0 to FFFFFFFF. For broadcastIcircuits, it is in the range 0 to FFFFFFFFFFFFFFFF.  %3 SOFTWARE_IDENTIFICATION software-idLIdentifies the name of the software to be to be downline loaded. 3 SOFTWARE_TYPE file-typeDIdentifies a particular file type to be loaded first. There are fourpossible file-types:1  MANAGEMENT FILE SECONDARY LOADER TERTIARY LOADER SYSTEM3 TERTIARY LOADER file-specDIdentifies the file specification of a tertiary loader program which9performs the downline load function. 8 3 VIA circuit-id?Identifies a circuit over which the loading sequence is to takeplace. 3 Examples, NCP>LOAD NODE NYC HOST BOSTON VIA FZA-1> This command initiates a downline load operation for = node NYC over circuit FZA-1. When loaded, node NYC A will have node BOSTON as the default host specification. NCP>LOAD NODE BANGORB This command initiates a downline load operation for node@ BANGOR. Any required default information is retrieved 9 from the volatile database on the executor node.; NCP>LOAD NODE SWIFT PHYSICAL ADDRESS AA-00-04-00-07-04@ This command initiates the downline load operation for B node SWIFT. The executor node uses the physical address 8 specified in the command to address node SWIFT.2 VIACUse the LOAD VIA command to downline load software to a target nodeDusing the specified circuit. The target node identification this isAassociated with the service circuit is obtained from the volatileDdatabase on the executor node. If the target node is on a broadcastAcircuit, the PHYSICAL ADDRESS parameter must be specified in thiscommand.  +LOAD VIA circuit-id (parameters ...)@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ADDRESS node-addressDIdentifies the address that the target node is to use (when it comesup). 3 CPU cpu-typeDIdentifies the target node's CPU type. There are four possibilities: DECSYSTEM1020 PDP11 PDP8 VAX3 FROM file-specAIdentifies the file specification of the load file containing the&system software to be downline loaded.3 3 HOST node-idCIdentifies the default host that the target node is to use (when it comes up).: 3 LOAD_ASSIST_AGENT file-specESpecifies the OpenVMS image that will define the system software for Ddownline loading the target node. The load assist agent can be usedBto tailor the system software to be loaded. The LOAD ASSIST AGENT;parameter applies to downline load operations to Local AreaVAXclusters only. 3 LOAD_ASSIST_PARAMETER itemDSpecifies a parameter to be passed to a load assist agent. The LOADCASSIST PARAMETER value applies to downline load operations to LocalArea VAXclusters only. 3 MANAGEMENT FILE file-spec?Specifies a file containing management information for downlineloading to the target node.3 NAME node-nameFIdentifies the name that the target node is to use (when it comes up).3 PHYSICAL ADDRESS p-addressCApplies only to broadcast circuits. Specifies the address that theEtarget node to be downline loa ded currently uses to identify itself. BThe value is the physical address that the target node has set forAitself or, if the target node has not set a physical address, theEhardware address associated with the target node's device controller.3 SECONDARY LOADER file-specEIdentifies the file specification of a secondary loader program which%performs the downline load operation.) 3 SERVICE_DEVICE device-typeFIdentifies the target node's line controller for the service line overFwhich the operation is to take place. See HELP PARAMETERS DEVICE-TYPEfor a list of devices.( COnly the synchronous port on the DMF service device may be used forservice operations. 3 SERVICE_PASSWORD hex-passwordFIdentifies the password required to trigger the bootstrap mechanism onBthe target node. The password is a hexadecimal number. For DDCMP=circuits, it is in the range of 0 to FFFFFFFF. For broadcast3circuits, it is in the range 0 to FFFFFFFFFFFFFFFF.' %3 SOFTWARE_IDENTIFICATION software-idLIdentifies the name of the software to be to be downline loaded. 3 SOFTWARE_TYPE file-typeDIdentifies a particular file type to be loaded first. There are fourpossible file-types:&  MANAGEMENT FILE SECONDARY LOADER TERTIARY LOADER SYSTEM3 TERTIARY LOADER file-specDIdentifies the file specification of a tertiary loader program which$performs the downline load function.8 3 Examples NCP>LOAD VIA DMP-0.4? This command initiates a downline load operation over ? circuit DMP-0.4. Any required default information is > retrieved from the volatile database on the executor = node. The node database is scanned until a node is > found whose service circuit matches the load circuit.6 NCP>LOAD VIA DMC-0 SOFTWARE TYPE SECONDARY LOADER? This command initiates a downline load operation over = circuit DMC-0, commencing with the secondary loader  file.: NCP>LOAD VIA UNA-0 PHYSICAL ADDRESS AA-00-04-00-07-04? This command initiates a downline load operation over : Ethernet circuit UNA-0, to the target node whose 6 physical address is specified in the command.! ww7 ,1 LOOP>Use the LOOP CIRCUIT, LOOP EXECUTOR, LOOP LINE, and LOOP NODE <commands to test specified components in the network. Each >command causes test blocks of data to be transmitted over the Aspecified components. The parameters can be entered in any orderBand are optional, except in the case of broadcast circuit loopbackCtests which require a parameter to define the loopback destination..LOOP CIRCUIT circuit-id (parameters ...)  EXECUTOR  LINE line-id  NODE node-id  2 CIRCUIT?Use the LOOP CIRCUIT command to test a specified circuit in the=network. This command does not apply to X.25 circuits. The 8parameters are optional and can be entered in any order.@LOOP CIRCUIT circuit-id ASSISTANT PHYSICAL ADDRESS p-address2 ASSISTANT NODE node-id( COUNT number* HELP help-type) LENGTH number( NODE node-id6 PHYSICAL ADDRESS p-address WITH# MIXED" ONES$ ZEROES @All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ASSISTANT_NODE node-idFApplies only to broadcast circuits. Identifies the name of the node or>the address of the node that will perform the role of loopback>assistant for broadcast third-party loop testing. If the HELPBparameter is specified, you must specify either the ASSISTANT NODE6parameter or the ASSISTANT PHYSICAL ADDRESS parameter.&3 ASSISTANT_PHYSICAL_ADDRESS p-addressEApplies only to broadcast circuits. Identifies the physical addressAof the node that will perform the role of loopback assistant forFthird-party loop testing. The address cannot be a multi cast address. ?If the HELP parameter is specified, you must specify either theEASSISTANT NODE parameter or the ASSISTANT PHYSICAL ADDRESS parameter., 3 COUNT numberFSpecifies the number of blocks to be sent during loopback testing overDthe circuit. The count must be a decimal integer in the range of 1 Ethrough 65535. If the parameter is omitted, only one block is looped.+ 3 HELP help-type=Applies only to broadcast circuits. Indicates the amount of Cassistance to be provided during broadcast loopback testing by theDassistant node, whose address is specified in the ASSISTANT PHYSICALAADDRESS or node-id as specified in the ASSISTANT NODE parameter. -There are three possible values of help-type: 9 TRANSMIT The assistant node relays the request to the< destination node, which replies directly to the executor node.@ RECEIVE The executor node sends the request directly to the< destination node, which relays the reply to theB assistant node for transmission to the executor node.@ FULL The assistant node relays the request and the reply@ between the executor node and the destination node.DIf HELP is specified, either ASSISTANT PHYSICAL ADDRESS or ASSISTANT,NODE must also be specified. 3 LENGTH number?Specifies the length (in bytes) of t he blocks to be sent duringDloopback testing. The length must be a decimal integer in the rangeAof 1 through 4096. Note that the LENGTH parameter must be less Fthan 50 for the DMC-11 circuit operating in either controller loopback?mode or cable loopback mode (a DMC-11 with an attached loopbackDcable). If the parameter is omitted, a block length of 4096 bytes isused.+ 3 NODE node-idFApplies only to broadcast circuits. Identifies the destina tion node toDbe used for loopback testing of the specified broadcast circuit. YouAcan use this parameter instead of the PHYSICAL ADDRESS parameter./ 3 PHYSICAL ADDRESS p-addressDApplies only to broadcast circuits. Identifies the physical address?of the destination node to be used for loopback testing of theCspecified broadcast circuit. You can use this parameter instead ofthe NODE node-id parameter..  3 WITH data-typeDSpecifies the type of binary information to be sent during testing. FIf you omit this parameter, a combination of ones and zeros (MIXED) is*sent. Three types of data can be sent: -  MIXED ONES ZEROS 3 Examples- NCP>LOOP CIRCUIT DMC-0 COUNT 5 LENGTH 20> This command initiates a circuit-level loopback test 6 over circuit DMC-0. The software loops five 8 messages, 20 bytes in length with mixed binary  information.> NCP>LOOP CIRCUIT UNA-0 PHYSICAL ADDRESS AA-00-04-00-FF-04> This command initiates a circuit-level loopback test A with a node whose physical address is AA-00-04-00-FF-04.+ NCP>LOOP CIRCUIT UNA-0 NODE 3.224 9 This command initiate an Ethernet circuit-level ? loopback test with a node whose address is 3.224. In B this example, the NODE parameter with a node-id of 3.224 @ was used in place of the PHYSICAL ADDRESS parameter. . NCP>LOOP CIRCUIT UNA-0 PHYSICAL ADDRESS -9 _ AA-00-04-00-12-04 ASSISTANT NODE GULL HELP RECEIVEA This command initiates a circuit-level loopback test by B transmitting a message directly to a node whose physical B address is AA-00-04-00-12-04. Additionally, the command E requests the assistance of a node named GULL to receive the F message from the target node and then relay the message back. 2 EXECUTORGUse the LOOP EXECUTOR command to test the executor node by causing testIdata to be transmitted to the executor node. The parameters are optionalHand can be entered in any order. You can supply explicit access controlJinformation for the LOOP EXECUTOR command. This command does not apply toVAX PSI., %LOOP EXECUTOR ACCOUNT account"  COUNT number# LENGTH number' PASSWORD password) USER user-id  WITH MIXED ONES ZEROS3 ACCOUNT account=Identifies the user's account for access control verificationfor the executor node.3 COUNT number9Specifies the number of blocks to be sent during loopback<testing over the executor node. The number must be a decimal<integer in the range of 1 through 65535. If the parameter is"omitted, only one block is looped.3 LENGTH number8Specifies the length (in bytes) of the blocks to be sent5during loopback testing. The length must be a decimal;integer in the range of 1 through 4096. If the parameter is.omitted, a block length of 4096 bytes is used.3 PASSWORD password>Identifies the user's password for access control verificationfor the executor node.3 USER 7Specifies the user's identification for access control #verification for the executor node.3 WITH :Specifies the type of binary information to be sent during)testing. Three types of data can be sent: MIXED ONES ZEROS<If omitted, a combination of ones and zeros (MIXED) is sent. 3 Example NCP>LOOP EXECUTOR@ This command initiates a loopback test on the executor  node.2 LINEDUse the LOOP LINE command to initiate loopba ck testing of X.25 linesConly. The parameters are optional and can be entered in any order.CBefore beginning loopback testing of an X.25 line, use the SET LINEDcommand to set the STATE, SERVICE and CONTROLLER LOOPBACK parametersBfor internal loopback testing or the STATE SERVICE and CONTROLLER 1NORMAL parameters for all other loopback testing.(LOOP LINE line-id COUNT number+ LENGTH number WITH#  MIXED" ONES# ZEROS3 COUNT numberFSpecifies the number of blocks to be sent during loopback testing over?the line. The count must be a decimal integer in the range of 1Ethrough 65535. If the parameter is omitted, only one block is looped.+ 3 LENGTH number?Specifies the length (in bytes) of the blocks to be sent duringDloopback testing. The length must be a decimal integer in the range @of 1 through 4096. If the parameter is omitted, a block length of 4096 bytes is used.* 3 WITH data-type:Specifies the type of binary information to be sent during)testing. Three types of data can be sent: MIXED ONES ZEROS<If omitted, a combination of ones and zeros (MIXED) is sent. 3 Examples  NCP>LOOP LINE DUP-0 @ This command initiates a line-level loopback test over E X.25 line DUP-0. The software loops one message, 4096 bytes2 in length, with mixed binary information.+ NCP>LOOP LINE DUP-1 COUNT 10 WITH ONES? This command initiates a line-level loopback test overE X.25 line DUP-1. The software loops 10 messages, 4096 bytes5 in length, with all binary ones information.2 NODEDUse the LOOP NODE command to test a specified node in the network by?causing test blocks of data to be tran smitted to the node. TheBparameters are optional and can be entered in any order. You canGsupply explicit access control information for the LOOP NODE command.  4To test the executor, use the LOOP EXECUTOR command.*LOOP NODE node-id ACCOUNT account' COUNT number( LENGTH number, PASSWORD password. USER user-id  WITH"  MIXED! ONES" ZEROS3 ACCOUNT accountEIdentifies the user's account for access control verification for thedesignated node.3 COUNT numberFSpecifies the number of blocks to be sent during loopback testing over?the node. The count must be a decimal integer in the range of 1Fthrough 65535. If the parameter is omitted, only one block is looped. 3 LENGTH number?Specifies the length (in bytes) of the blocks to be sent duringDloopback testing. The length must be a decimal integer in the range Hof 1 through 4096. If the parameter is omitted, a block length of 4096bytes is used. 3 PASSWORD passwordFIdentifies the user's password for access control verification for thedesignated node. 3 USER user-idCSpecifies the user's identification for access control verificationfor the designated node. 3 WITH data-typeDSpecifies the type of binary information to be sent during testing. .Three types of data can be sent:  MIXED ONES ZEROS<If omitted, a combination of ones and zeros (MIXED) is sent. 3 Example& NCP>SET NODE TESTER CIRCUIT FZA-0 NCP>LOOP NODE TESTER" NCP>CLEAR NODE TESTER CIRCUIT@ The first command creates a loop node name (TESTER) forA the associated circuit. The second command initiates a ? node-level loopback test with the loop node name. TheC third command removes the loop node name from the volatileO database when the loopback is completed. ww7כ , 1 ParametersEMany parameters and components require user-supplied information whenDyou issue an NCP command. For the most part, their syntax follows aGstandard set of rules. Exceptions to these rules are documented in theGdescription of the parameter for which they apply. For the list below,Gall numeric values are in decimal and have a range of 0 to 65535 unlessotherwise specified.@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 2 account EA string of up to 39 alphanumeric and hyphen characters. Currently, :OpenVMS systems do not use this string for access control. 2 area-numberFA decimal value in the range 1 to 63 to be specified in the beginning Hof the node-address and separate d from the node number by a period. If Fyou do not specify an area number, the area number of the executor is 4used. The default area number for the executor is 1. 2 circuit-idFA string of characters whose exact syntax is that for a DECnet OpenVMSJcircuit. The string may also be that for an X.25 circuit identification,Ifor systems that include this configuration. For X.25 circuits using VAXDP.S.I., circuit-id is a string of up to 15 characters beginning with"X25-". :Circuit identification takes one of the following formats:dev-cdev-c-udev-c.t dev-c-u.tBdev Is a device name. Refer to HELP PARAMETERS DEVICE-TYPE for & a list of device mnemonic names.?c Is a decimal number (0 or a positive integer) designating' the device's hardware controller.Cu Is a decimal unit or circuit number (0 or a positive integer)@ included only if more than one unit is associated with the controller.Ct Is a decimal number (0 or a positive integer) that identifies= a tributary on a multipoint circuit. This is a logical3 tributary address used to poll the tributary. 2 cpu-type :A string of characters consisting of one of the following: DECSYSTEM20 PDP11 PDP8 VAX 2 dest-name GAn identification string consisting of 1 to 16 alphanumeric characters. 2 device-typeEA string of characters representing the mnemonic name for the device.)MNEMONIC DRIVER PROTOCOL DESCRIPTIONG----------------------------------------------------------------------->BNA ET ETHERNET DEBNA, DEBNI communications linkFCI CN CI-780, CI-750, CIBCA, or CIBCI computer* interconnect3DIV SD DDCMP DIV32 ISDN controller9DMB SI DDCMP DMB32 synchronous line unit<DMC XM DDCMP DMC11, DMR11 synchronous links9DMF XG DDCMP DMF32 synchronous line unitEDM P XD DDCMP DMP11, DMV11 synchronous point-to-point8 or multipoint line devices9DSB SL DDCMP DSB32 synchronous line unit;DSF SF DDCMP For VAXft 3000 series systemsEDST ZS DDCMP DST32, DSH32 synchronous circuit device>DSV SJ DDCMP DSV11 synchronous line interface@DSW ZT DDCMP DSW-21, DSW-41, DSW-42 synchronous3 communication devices< FQA FQ FDDI DEFQA FDDI communications link<FZA FC FDDI DEFZA FDDI communications link6ISA EZ ETHERNET SGEC communications link<KFE EF ETHERNET VAXft 3000 communications link<MFA FX FDDI DEMFA FDDI communications link7MNA EX ETHERNET DEMNA communications link6MXE EC ETHERNET PMAD communications linkGQNA XQ ETHERNET DEQNA, DELQA, DESQA, DEQTA communications" link7SVA ES ETHERNET DESVA communications linkCTT NO DDCMP DZ11, DZ32, DZQ11, DZV11 asynchronous- circuit devices@TX NO DDCMP DMB32, DHB32, DHU11, DHV11, DHT32,G DMF32 or DMZ32, DHQ11, DMB3L asynchronousG circuit devices, CXY08, DSH32 synchronous= or asynchronous circuit devices@UNA XE ETHERNET DEUNA or DELUA communications link 2 dte-addrHA string of up to 15 decimal digits. See the Public Network Information>Manual for the exact format of this parameter on your network. 2 event-listHA list of event types for a given class in the format class.type. When Jspecifying an event list, you may specify only one class; however, you can:specify a range of types by using commas and hyphens, for Fexample, 4.3-5,7-10. You can use an asterisk wildcard character in anC event list, but only to replace an event type. The following table#provides examples of these formats. F EVENTS EVENT LIST L Event class 4, type 4 4.4 L Event class 4, types 5 through 7 4.5-7 / Event class 4, types 5, 7 through 9, and 11 G Note that types must be specified in ascending order 4.5,7-9,11 > Event types for class 4 events 4.*+See HELP EVENTS for a list of valid events. 2 file-specEAn OpenVMS file specification string in the following general format:2node-spec::device:[directory]filename.type;version<Logical names are permitted. The maximum length for a file Especification in DECnet for OpenVMS is 127 characters. Refer to the >OpenVMS DCL Concepts Manual for the format of an OpenVMS file Cspecification, and the Guide to OpenVMS File Applications for more #information about specifying files. 2 h-address:A string of 6 hexadecimal bytes separated by hyphens (for Aexample, 08-00-2B-2B-AF-F3). The string represents the hardware #address of a LAN device controller. 2 hex-byte)A string of exactly 2 hexadecimal digits.2 hex-password'A string of up to 8 hexadecimal digits. 2 hex-value(A string of up to 32 hexadecimal digits. 2 id-stringHA string of up to 32 characters. If the string includes spaces or tabs,"enclose it within quotation marks. 2 line-id CA string of characters whose exact syntax is that for a DECnet for FOpenVMS line identification. The string may also be that for an X.25 Fline identification, for systems that include this configuration. ForAOpenVMS operating systems, the line-id takes one of the followingformats:dev-cdev-c-uEdev Is a device name. See HELP PARAMETERS DEVICE-TYPE for a list ) of possible device mnemonic names.Dc Is a decimal number (0 or a positive integer) designating the$ device's hardware controller.Au Is a decimal unit or line number (0 or a positive integer)A included if the device is a multiple unit line controller.2 microsecondsA decimal numeric value.2 millisecondsA decimal numeric value. 2 net-nameJFor X.25 circuits, specifies a 1- to 16-character alphanumeric identifier &that indicates the network to be used. 2 node-addressDA numeric value in the range of 1.1 to 63.1023, composed of an area Gnumber to the left of the period followed by a non-zero node number to Hthe right of the period. (The node number indicates the address of the Jnode within the specified area.) If the area number is not supplied, the Earea number of the executor is used. The default area number for theexecutor is 1. 2 node-id%Either a node-name or a node-address.2 node-name DA string of up to 6 alphanumeric characters containing at least one alphabetic character.2 node-spec GA node-id followed by optional access control information as specified for OpenVMS in the form: node-id"user password"2 node-type :A string of characters consisting of one of the following: ROUTING III NONROUTING III ROUTING IV NONROUTING IV AREA 2 number A decimal numeric value. 2 object-nameEA string of up to 16 printable characters, consisting of alphanumeric7characters, the dollar sign ($), or the underscore (_). 2 p-address;A string of 6 hexadecimal bytes, separated by hyphens (for ?example, 08-00-2B-2B-AF-F3). The value is the unique physical Aaddress that the node has set for itself or, if the node has not Aset a physical address, the hardware address associated with the node's device controller. 2 password,A string of up to 39 printable characters. 2 privilege-list@A list of OpenVMS privilege names delimited by space characters. 2 secondsA decimal numeric value. 2 sink-nameG A string of alphanumeric characters that specifies the name of an eventDsink. The logging console name is a string in the form TTcnn (if a Fterminal) or a file specification if it is a file that receives eventsGin console format. The logging file name is a file specification. TheAlogging monitor name is a 1- to 9-character name. If the string 7includes spaces or tabs, enclose it in quotation marks. 2 software-id A string of up to 16 characters.2 software-type:A string of characters consisting of one of the following: MANAGEMENT FILE SECONDARY LOADER TERTIARY LOADER SYSTEM2 tributary-address)A numeric value in the range of 0 to 255. 2 user-id8A string of up to 12 alphanumeric and hyphen characters.! ww7כ , 1 PromptingBNCP prompts for required components and parameters if they are notEsupplied when you issue the command. Each prompt is either a list ofBadmissible keywords for that position in the command syntax or the<name of a parameter and a description of the value required.EPrompting will not occur when NCP receives input from a command file.5Parameter keywords must be supplied in command files.GEach prompt consists of two parts: the component or parameter desired,5and its format. The format of prompts is as follows: Component (Format):@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 2 Format _of_prompts@The component part indicates the name of either the component orEparameter. The format part indicates the range of acceptable values.@The format part presents keywords in uppercase, value classes inClowercase as descriptive strings, and numeric ranges as two numbersGseparated by a hyphen. Commas indicate alternatives which are mutually exclusive. 2 Exiting_the_Prompting_SequenceCYou can exit a prompting sequence by responding with CTRL/Z for theDprompt. This returns you to the NCP> prompt where you can then issueAanother NCP command. You can exit NCP directly from the prompting-sequence by responding with CTRL/C or CTRL/Y.@Responding to a parameter prompt or query with "_DONE" skips the>remainder of the prompts or queries and performs the requestedFfunction with the parameters which have been entered up to that point. 2 ExamplesCThe following examples illustrate three types of prompting that NCP provides.5Prompts to supply missing command component keywords: NCP>CLEAR 6 (LINE, CIRCUIT, LOGGING, KNOWN, NODE, OBJECT):FNo component is specified for the CLEAR command. The prompt format isBa list of admissible component keywords separated by commas. Note7that the plural keyword KNOWN is included in this list.#Prompts to supply parameter values: NCP>CLEAR LINE  LINE ID (dev-c-u.t):HNCP prompts for the line-id for this component since it is not provided with the command.BThe following example shows variations of the prompting scheme forparameter values: NCP>SET EXECUTOR 2 Node address (1.1-63.1023): 2.110 State (ON, OFF, SHUT, RESTRICTED): ON ...1 Pipeline quota (0-65535 bytes):6000"Prompts to select parameter names: NCP>CLEAR LINE ( Line ID (dev-c-u.t): DMC-1" All line parameters (Y,N):CNCP prompts for the selected parameter names whose values are to beIremoved from the database. In this case, no parameter name was given; Jconsequently, NCP asks if all values should be removed. Y indicates Hthat all values should be removed. N causes NCP to provide a different response. For example,% NCP>CLEAR NODE BOSTON $ All node parameters (Y,N): N$ Host node (Y,N): Y$ Identification (Y,N): N ...$ Service password (Y,N): Y$ Tertiary loader (Y,N): NFSince N is the response to the first prompt above, NCP prompts for allof the parameter names.! wwW ,1 PURGEAUse the PURGE command to remove selected parameters or componentsFfrom the permanent database. See HELP CLEAR for a description of the parameters which may be removed.! 2 CIRCUITDUse the PURGE CIRCUIT command to remove circuit parameters from the Epermanent database on the local node or DTE. See HELP CLEAR CIRCUIT 9for a description of the parameters which may be removed. 2 EXECUTORGUse the PURGE EXECUTOR command to remove selected local node parametersGfrom the permanent database on the local node. See HELP CLEAR EXECUTOR4for a list of the parameters which may be specified.2 LINEGUse the PURGE LINE command to remove line parameters from the permanentIdatabase on the local node or DTE. See HELP CLEAR LINE for a descriptionFof the parameters which may be specified. 2 LOGGINGCUse the PURGE LOGGING command to remove logging parameters from theHpermanent database on the local node or DTE. See HELP CLEAR LOGGING for0a list of the parameters which may be specified. 2 MODULE 'Introduces the various module entities.3 CONFIGURATORFUse the PURGE MODULE CONFIGURATOR command to remove from the permanentEdatabase at the local node the Ethernet configurator module componentAparameters for the circuit or circuits specified. See HELP CLEAR*MODULE CONFIGURATOR for more information.  3 X25-ACCESS ?Use the PURGE MODULE X25-ACCESS command to remove network names<from the permanent data base or to remove individual network6parameters. See HELP CLEAR MODULE X25-ACCESS for more information.3 X25-PROTOCOLFUse the PURGE MODULE X25-PROTOCOL command to remove the parameters of Dthe Protocol Module component from the permanent database. See HELP7CLEAR MODULE X25-PROTOCOL for more information. 3 X25-SERVER CUse the PURGE MODULE X25-SERVER command to remove the parameters ofCthe X.25 Call Handler from the permanent data base. See HELP CLEAR5MODULE X25-SERVER for more information.  3 X29-SERVERCUse the PURGE MODULE X29-SERVER command to remove the parameters ofCthe X.29 Call Handler from the permanent data base. See HELP CLEAR'MODULE X25-SERVER for more information.? 2 NODEFUse the PURGE NODE command to remove node parametersfrom the permanentEdatabase on the executor node. See HELP CLEAR NODE for a list of the@parameters which may be specified. * 2 OBJECTKUse the PURGE OBJECT command to remove object parameters from the permanentGdatabase on the executor node. See HELP CLEAR OBJECT for a list of the"parameters which may be specified.6 ww1 ,1 SET CUse the SET command to create or modify parameters or components inCthe volatile database on the executor node. Use the DEFINE commandFto create or modify parameters or components in the permanent databaseon the executor node. 2 CIRCUIT7Use the SET CIRCUIT command to create or modify circuit?parameters in the volatile database. Most parameters cannot be<SET when the circuit is in the ON state. However, the COST,<COUNTER TIMER, HELLO TIMER, MAXIMUM ROUTERS, STATE, TRANSMITATIMER, and VERIFICATION can be changed with the circuit is in the&ON state.  -SET KNOWN CIRCUITS (parameters ...)DEFINE CIRCUIT circuit-id<Use the DEFINE CIRCUIT command to create or modify permanentcircuit parameters. @All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ALLAUse the ALL command to update the volatile database with all the ?circuit parameters stored for a particular circuit or all known#circuits in the permanent database.3 ACTIVE_BASE baseAApplies to DDCMP CONTROL circuits. This value indicates the base<priority of an ACTIVE tributary after the tributary has been9polled. You can indicate a separate base for each of the;indicated polling states. The base value must be a decimalBinteger from 0 to 255. The ACTIVE BASE default is 255. " 3 ACTIVE_INCREMENT increment?Applies to DDCMP CONTROL circuits. This parameter indicates the@increment value added to the ACTIVE tributary priority each time<the scheduling timer expires. The increment value must be aCdecimal integer from 0 to 255. The ACTIVE INCREMENT default is 0.  3 BABBLE TIMER milliseconds ?Applies to DDCMP CONTROL circuits. It represents the number of<milliseconds that a selected tributary or remote half-duplex?station is allowed to transmit. Milliseconds must be a decimal9integer in the range 1 to 65 535. The default is 6000 (6 seconds). 8 3 CHANNEL number AApplies only to X.25 PVCs. Identifies the logical channel numberAfor the X.25 PVCs. Specify a value in the range 0 to 4095. ThisAparameter is mandatory when you specify an X.25 PVC for the first7time. - 3 CIRCUIT circuit-id?Identifies the circuit for which specified parameters are to be$created or modified in the database. 3 COST number=Does not apply to X.25 PVCs. Specifies the transport routingAcost of the circuit. The number must be a decimal integer in the<range 1 to 63. Messages will travel between nodes along theFpath with the smallest total cost.  3 COUNTER TIMER seconds>Specifies the number of seconds that the circuit counter timer=will run. When the counter timer expires , a circuit counter@logging event occurs. Seconds must be a decimal integer in the<range 0 to 65535. If no value is set for COUNTER TIMER, the/circuit counters are not logged automatically.  3 DEAD THRESHOLD countAApplies only to DDCMP CONTROL circuits. It defines the number of=times to poll the active, inactive, or dying tributary before:changing that tributary's polling state to DEAD because ofAreceive timeouts. Count must be a decimal integer in the range 0"to 255. The default count is 8.  3 DTE dte-addr=Applies only to X.25 PVCs and DLM circuits. It identifies the@local DTE for the circuit. Specify a decimal integer of 1 to 15Adigits. See the Public Network Information manual for the format?of the address on your network. This parameter is optional for>DLM SVCs and mandatory when you specify an X.25 PVC or DLM PVCfor the first time. 3 DYING_BASE base ;Applies to DDCMP CONTROL circuits. This value sets the base:priority of a Dy ing tributary after the tributary has been>polled. You can set a separate base for each of the indicated?polling states. Base must be a decimal integer from 0 to 255. The DYING BASE default is 0.  3 DYING_INCREMENT increment:Applies to DDCMP CONTROL circuits. This parameter sets the?increment value added to the DYING tributary priority each timeAthe scheduling timer expires. Increment must be a decimal integer3from 0 to 255. The DYING INCREMENT default is 16. - 3 DYING_THRESHOLD number >Applies to DDCMP CONTROL circuits. It specifies the number of>times to poll the active or inactive tributary before changing:that tributary's polling state to DYING because of receive>timeouts. Number must be a decimal integer in the range 0 to1255. The default number is 2. 3 HELLO TIMER seconds @Does not apply to X.25 PVCs. Specifies the frequency of Routing?Hello message s sent to adjacent nodes on the circuit. Seconds=must be a decimal integer in the range 0 to 8191. The defaultAvalue is 15. The value of the read-only circuit parameter LISTEN?TIMER is three times the value of the HELLO TIMER parameter. $ 3 INACTIVE_BASE base@Applies to DDCMP CONTROL circuits. This value indicates the base>priority of an INACTIVE tributary after the tributary has been9polled. You can indicate a separate base for each of the@indicated polling states. Base must be a decimal integer from 0to 255. The default is 0.  3 INACTIVE_INCREMENT increment?Applies to DDCMP CONTROL circuits. This parameter indicates the=increment value added to the INACTIVE tributary priority each>time the scheduling timer expires. Increment must be a decimal+integer from 0 to 255. The default is 64.  3 INACTIVE_THRESHOLD number>Applies to DDCMP CONTROL circuits. It specifies the number of7times to poll the active tributary before changing that8tributary's polling state to inactive because of no data;response. Number must be a decimal integer in the range 0 !to 255. The default number is 8. + 3 KNOWN CIRCUITS>Indicates that the specified parameters for all known circuits.are to be created or modified in the database.3 MAXIMUM_BUFFERS number<Applies to DDCMP CONTROL circuits. It specifies the maximum>number of buffers from a common buffer pool that the tribu tary>can use. If you do not set this parameter, there is no common;buffer pool and the higher level will explicitly supply theAbuffers. Number must be a decimal integer in the range up to 254!or the keyword UNLIMITED.  3 MAXIMUM_DATA numberBApplies only to X.25 PVCs and DLM circuits. Specifies the maximum =packet size for the X.25 circuit. This value must be at least@five bytes less than the MAXIMUM BLOCK value that you specify in;the SET or DEFINE LINE command, and must be a power of two..Specify a value in the range 16 to 4096 bytes. ABy default, packet size takes the value specified by the PROFILE @parameter of the SET or DEFINE MODULE X25-PROTOCOL command. See?the Public Network Information manual for the network value ofthis parameter.= 3 MAXIMUM_RECALLS number;Applies only to X.25 DLM outgoing Switched Virtual Circuits?(SVCs). Specifies the maximum number of call retries generated9on an outgoing DLM circuit before the circuit is declaredAnonoperational. The range of possible values for MAXIMUM RECALLS@is 0 to 255. The number value of 0 specifies an infinite number+of call retries. The default value is 100. 3 MAXIMUM_ROUTERS number =Applies only to broadcast circuits. It specifies the maximum@number of routers allowed by the Routing layer on this circuit. <Use a number in the range 1 to 33. The default value is 33. 3 MAXIMUM_TRANSMITS number<Applies to DDCMP CONTROL circuits. It specifies the maximum<number of data messages that can be transmitted at one time.<Number must be a decimal integer in the range 1 to 255. Thedefault is 4.  3 MAXIMUM_WINDOW count>Applies only to X.25 PVCs and X.25 DLM circuits. Specifies the?maximum window size allowed for the X.25 circuit--that is, the?maximum number of packets for which outstanding acknowledgments@are allowed. Specify a value in the range 1 to 127. ?By default window size takes the value specified by the PROFILE@parameter of the SET or DEFINE MODULE X25-PROTOCOL command. See>the Public Network Information manual for the network value ofthis parameter.= 3 NETWORK net-name>Applies only to X.25 PVCs and X.25 DLM circuits. Specifies the>network that the circuit runs through. If only one network is8set up, this parameter is not r equired. Otherwise, theparameter is mandatory.3 NUMBER dte-addr?Applies only to X.25 DLM Switched Virtual Circuits (SVCs). For 7outgoing circuits, specifies the remote DTE address and9subaddress that this DLM circuit will call. For incoming=circuits, specifies the address of the remote DTE from which>this circuit will accept calls. If the NUMBER parameter is not>specified for an incoming circuit, a call from any remote DTE@can be directed to this circuit. Specify a decimal integer of 1 to 15 digits.3 OWNER EXECUTOR @Applies only to X.25 DLM circuits. Identifies the circuit owner=as the executor. This parameter is mandatory for an X.25 DLM circuit. 4 3 POLLING STATE stateCApplies only to DDCMP CONTROL circuits. Identifies the multipoint @polling state of the tributary. There are five possible states:) > AUTOMATIC The tributary's state varies according to the A operation of the polling algorithm. This is the  default.< ACTIVE The tributary is locked in the ACTIVE state.> INACTIVE The tributary is locked in the INACTIVE state.; DYING The tributary is locked in the DYING state.: DEAD The tributary is locked in the DEAD state.3 RECALL TIMER seconds;Applies only to X.25 DLM circuits. Specifies a timer whose;expiration causes a remote DTE to be called again during an>attempt to set up a DLM circuit. Specify a decimal integer inthe range 1 to 65535. 3 ROUTER PRIORITY number@Applies only to broadcast circuits. Specifies the priority this<router (the executor node on this circuit) is to have in the@selection of designated router for this circuit. Use a value in,the range 0 to 127. The default value is 64.3 SERVICE mode:Does not apply to X.25 circuits. Specifies whether or notAservice operations (loading and loop testing) are allowed for the*circuit. There are two possible modes: :DISABLED The circuit may not be put into service state ; and may not perform service functions. This is  the default.:ENABLED The circuit may be put into service state and & perform service functions.3 STATE circuit-state:Specifies the circuit's operational state. There are threepossible states: D $OFF The circuit is not in use.=ON The circuit is available for normal use or service  functions.;SERVICE The line is available for service functions only.3 TRANSMIT TIMER milliseconds@Applies to DDCMP circuits. Specifies the number of milliseconds@to delay between data message transmits. Milliseconds must be aCdecimal integer in the range 0 to 65535. The default is 0. C 3 TRIBUTARY tributary-address<Applies to DDCMP circuits. Indicates the Data Link physical>tributary address of the circuit. The tributary-address value1must be a decimal integer in the range 0 to 255. - 3 TYPE X25 ?Applies only to X.25 circuits. Specifies the type of circuit. <For circuit names starting with "X25-", TYPE is always X25.  3 USAGE >Usage-type Applies only to X.25 circuits. Specifies the usageAtype of an X.2 5 virtual circuit. The possible values usage-typesare: 2 ?INCOMING Applies only to X.25 DLM SVCs. The circuit is used $ only for incoming calls. ?OUTGOING Applies only to X.25 DLM SVCs. The circuit is used $ only for outgoing calls. 7PERMANENT This parameter is mandatory for X.25 PVCs. ; The circuit is permanently connected to a remote> DTE, and does not need to be switched dynamically. 3 VERIFICATION option?Applies only to synchronous and asynchronous circuits. Requires<the remote node to send its routing initialization password.'There are three options: = DISABLED Does not require the remote node to send its > routing initialization password. This is the  default.= ENABLED Requires the remote node to send its routing + initialization password. ? INBOUND Applies to any D DCMP point-to-point circuits. < Specifies that the executor node expects to > receive a routing initialization password for 9 verification from a remote node before a ; connection is made between the nodes. The ? executor is prohibited from sending its routing= initialization password to the remote node. > This parameter is specified automatically for 9 dynamic asynchronous DDCMP circuits. If A VERIFICATION INBOUND is specified for a circuit, A the INBOUND parameter must be set for the remote 9 node (using the SET/DEFINE NODE COMMAND). 3 Examples NCP>SET KNOWN CIRCUITS ALLE This command loads all permanent database entries stored for7 all known circuits into the volatile database.* NCP>SET CIRCUIT DMC-0 COST 4 STATE ONE This command sets the STATE to ON and the circuit COST to 4  for circuit DMC-0.5 NCP>SET CIRCUIT MNA-0 STATE ON MAXIMUM ROUTERS 5D This command sets Ethernet circuit MNA-0 to ON and sets theA maximum number of routers permitted on the circuit to 5.< NCP>DEFINE CIRCUIT X25-ANDIES CHANNEL 3 DTE 123789456 -? _ NETWORK PSDND MAXIMUM DATA 1024 MAXIMUM WINDOW 7 USAGE - _ PERMANENT STATE ONB This command defines an X.25 PVC called X25-ANDIES with a; logical channel n umber of 3 on the local DTE with @ address 123789456 on network PSDND. The circuit has a @ maximum packet size of 1024 bytes and a maximum window  size of 7.B NCP>DEFINE CIRCUIT X25-DLM-0 NUMBER 456789012 NETWORK PSDNA - _ USAGE OUTGOING STATE ONC This command defines a DLM SVC called X25-DLM-0 connected D to the remote DTE on network PSDNA with address 456789012, % and used for outgoing calls.A NCP>DEFINE CIRCUIT X25-DLM-1 NUMBER 12345677 NETWORK PSDNB - _ USAGE INCOMING STATE ONC This command defines a DLM SVC called X25-DLM-1 on networkC PSDNB that accepts only incoming calls from the remote DTE with address 12345677.! NCP>SET CIRCUIT DMC-* COST 5E This command sets the circuit cost to 5 for all DMC circuits" in the volatile database.! 2 EXECUTORBUse the SET EXECUTOR command to create or modify parameters in theDvolatile database whic h controls the network on the executor node.  CAfter the executor node's state is set to ON, you cannot change its>ADDRESS, ALIAS NODE, BUFFER SIZE, SEGMENT BUFFER SIZE, MAXIMUM=BROADCAST ROUTERS, NAME, TYPE or MAXIMUM CIRCUITS parameters. EUse the DEFINE EXECUTOR command to create or modify parameters in theBvolatile database which controls the network on the executor node. (SET EXECUTOR (parameters ...)DEFINE @All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ALLCUse the SET EXECUTOR ALL command to update the volatile copy of theFexecutor node's database with all the local node parameters stored for$that node in its permanent database.3 ADDRESS node-address:Establishes a node address for the local node, in the form area-number.node-numberCwhere the area-number is in the range 1 to 63, and t he node number Bis in the range 1 to 1023. If the area-number is not specified, aDdefault value of 1 is assumed. You need not supply the area number Ain the node-address if your node is in area 1. This parameter is+required when you configure the local node. 3 ALIAS_INCOMING option>Specifies whether the local node is willing to accept incomingArequests directed to the alias node identifier specified for theClocal node. The alias node identifier is descri bed under the ALIAS=NODE parameter. There are two options for ALIAS INCOMING:  : ENABLED Specifies that the local node will accept @ incoming connect requests directed to the alias ; node identifier. This is the default if an9 alias node identifier has been specified.7 DISABLED Specifies that the local node will not 5 accept the incoming connect requests 6 directed to the alias node identifier.3 ALIAS_MAXIMUM_LINKS numberESpecifies the maximum number of logical links for the local node thatAcan use the alias node identifier. The alias node identifier isAdescribed under the ALIAS NODE parameter. The maximum value for 7ALIAS MAXIMUM LINKS is 200. The default value is 32.  3 ALIAS_NODE node-idGEstablishes a cluster alias node identifier for use by the local node. =The node-id is a DECnet node identifier that can be either a Enode-name or a node-address. This alias permits the local node to beCassociated with a cluster node identifier common to some or all theBnodes in a cluster, in addition to its own unique node-id. If thisCparameter is not specified, the local node is not associated with aCcluster alias node identifier. If a node-name is to be used as theEalias node-id, the node-name must previously have been defined in the database. 3 AREA_MAXIMUM_COST number CApplies only to an executor node whose type is AREA. Specifies theFmaximum total path cost allowed from the executor to any other level 2Grouting node. You can specify a decimal value in the range 1 to 1022. The default value is 1022. 3 AREA_MAXIMUM_HOPS numberCApplies only to an executor node whose type is AREA. Specifies theAmaximum number of routing hops allowable from the executor to anyCother level 2 routing node. You can specify a decimal value in the#range 1 to 30. The default is 30. !3 BROADCAST ROUTING TIMER secondsESpecifies the maximum amount of time allowed between Routing updatesFon broadcast circuits. When the timer expires before a routing updateCoccurs, a routing update is forced. The routing update produces aCrouting configuration message for each adjacent node. Routing usesCthis timer to enforce a minimum delay between routing updates. YouAcan specify a number in the range 1 to 65,535. The default value is 180. 3 BUFFER  SIZE number;Specifies in bytes the size of the receive buffers, thereby@controlling the maximum size of NSP message segments that can beDreceived and forwarded. The size includes protocol overhead down toCand including the End Communication layer, but does not include theCData Link layer overhead. This buffer size applies to all circuitsFknown to the executor. The default value is equal to the value of the@SEGMENT BUFFER SIZE, if specified; otherwise the default is 576.DThe value of  the BUFFER SIZE parameter must be greater than or equalFto the value of the SEGMENT BUFFER SIZE parameter. The two values areDnormally equal but may differ to permit the network manager to alterCbuffer size on all nodes without interruption of service. Refer toEthe DECnet for OpenVMS Networking Manual for information about how tomodify buffer sizes. 3 COUNTER TIMER seconds@Specifies a timer whose expiration causes a line counter loggingevent. 3 DEFAULT ACCESS optionCAs signs the default access to all nodes which do nothave a specificGnode ACCESS entry in the volatile data base. There are four options:  F INCOMING Allows logical link connections from the remote node. D OUTGOING Allows the local node to initiate connections to theE remote node, but does not allow connections from the  remote node.F BOTH Allows incoming and outgoing logical link connections.$ This is the default.A NONE Does not allow incoming or outgoing logical link ) connections to this node.DIf you have OPER privilege on the local system, you can override the7default access restriction specified in this parameter.3 DELAY_FACTOR number>Specifies the number by which to multiply one sixteenth of theDestimated round trip delay to a node to set the retransmission timerFto that node. Use a number in the range 16 to 255. The default value is 80. 3 DELAY_WEIGHT n umberBSpecifies the weight to apply to a new round trip delay data pointEwhen updating the estimated round trip delay to a node. Use a number2in the range of 1 to 255. The default value is 5.6 3 DNS_INTERFACE option=Specifies whether the local node will obtain node and addressDinformation from the DECdns namespace to update the node informationCin the volatile database. For information about using an existingBDECdns namespace for node-name-to-address mapping, see DECnet for1OpenVMS Networking Manual. There are two options:EENABLED Enables the use of the DECdns namespace, which must already9 exist, for updating the volatile node database.BDISABLED Specifies that the node will not use DECdns namespace toA search for node name and address information. Only the? local node database is searched for this information. This is the default.3 DNS_NAMESPACE string=Specif y this parameter if you want to use the DNS INTERFACE. ESpecifies an existing DECdns namespace used by the DNS interface. IfBDNS INTERFACE is ENABLED and you omit the DNS NAMESPACE parameter,CDECnet for OpenVMS uses the default DECdns namespace for node nameEand address lookups. This string value must be 1 to 256 alphanumericDcharacters, and can include the dollar sign ($), underscore (_), andhyphen (-) characters.3 IDENTIFICATION stringCSpecifies a text string that describes the executor node (thatFis, "Host System"). The string can be a maximum of 32 characters. IfDit contains blanks or tabs, you must enclose the string in quotationmarks. 3 IDP string=Specify this parameter if you want to use the DNS INTERFACE. ;Specifies the IDP of the network's network service access >point (NSAP) (global network address). This is a string of 1 -to 22 hexadecimal digits. The default is 49.3 INACTIVITY TIMER seconds@Specifies the maximum duration ofina ctivity (no data in eitherAdirection) on a logical link before the node checks to see if theDlogical link still works. The range is between 1 and 65,535. If you7do not specify this parameter, the default value is 60.# 3 INCOMING_PROXY option BIndicates whether proxy login requests present on incoming logical@links are to honored. There are two options for INCOMING PROXY:? DISABLED Ignores all incoming proxy requests. Instead, >  validates the logical link by using the access? control information associated with the object.7 ENABLED Invokes the appropriate proxy, based on; the source user, source node, and supplied = access control information (if any). This is the default.@Note that proxy access characteristics established in the object>database take preference over the proxy access characteristics%established in the executor database.  3 INCOMING_TIMER secondsBSpecifies the maximum amount of elapsed time between the time a?connection is received for a process and the time that processAaccepts or rejects the connection. For very busy systems, use aEvalue in the range of 45 to 60 seconds. Otherwise use a value of 30seconds. The default is 45.3 MAXIMUM_ADDRESS number BIndicates the largest node address and, consequently, the greatestAnumber of nodes within an area that can be addressed by the local"no de. The default is 1023.  >If you receive an "invalid value" error, you probably have notBallocated enough nonpaged pool space. You must lower the MAXIMUMCADDRESS value or increase the VMS NPAGEDYN value. (Use the System>Generation Utility (SYSGEN) to change the NPAGEDYN parameter.)3 MAXIMUM_AREA numberCApplies only to an executor node whose type is AREA. Specifies theElargest area number and, therefore, the greatest number of areas that@can be known  about by the executor node's Routing layer. You canAspecify a decimal value in the range 1 to 63. The default is 63.&3 MAXIMUM_BROADCAST_NONROUTERS number CSpecifies the maximum total number of nonrouting nodes (end nodes) Dthe executor node can have on its broadcast circuits. Use a number .in the range of 1 to 1023. The default is 64."3 MAXIMUM_BROADCAST_ROUTERS numberCSpecifies the maximum total number of routers the executor node canFhave on its broadcast circuits. The value of this parameter should be?obtained by multiplying 32 by the value of the executor MAXIMUM'CIRCUITS parameter. The default is 32. 3 MAXIMUM_BUFFERS numberESpecifies the maximum number of buffers in the transmit buffer pool. FDECnet normally allocates only what it needs. At minimum, use a valueBthat is 15 times the square root of the number of lines. IncreaseBthis value if you experience congestion loss. The default value is 100.3 MAXIMUM_CIRCUITS numberFSpec ifies the maximum number of circuits that the local node can use. >Number must be in the range 1 to 127. The default value is 16.3 MAXIMUM_COST numberDSpecifies the maximum total path cost allowed from the local node toBany node. The path cost is the sum of the line costs along a pathCbetween two nodes. Use as small a number as possible in the range #of 1 to 1022. The default is 1022. !3 MAXIMUM_DECLARED_OBJECTS numberFSpecifies the maximum number of objects that all processes on a systemEmay declare. To determine the current number of declared objects onAyour system, use the NCP SHOW KNOWN OBJECTS command. Each of theFobjects with a PID displayed is one declared object. A single process@can declare more than one object. You must provide a sufficient@number of objects for the network servers to be intialized. TheFdefault is 31, which is sufficient for most configurations. The valueErange of objects is 8 to 16383. Dynamically setting the number lowerEthan the number of declared objects currently in use has no effect onthose objects.3 MAXIMUM_HOPS numberCSpecifies the maximum routing hops from the local node to any otherEreachable node. A hop is the logical distance over a line between twoDadjacent nodes. Use as small a number as possible in the range of 1?to 30, and be sure that this value is less than or equal to the3MAXIMUM VISITS parameter. The default value is 30.3 MAXIMUM_LINKS numberFSpecifies the maximum number of logical links for the local node. TheFmaximum value for MAXIMUM LINKS is 3885. The default value of MAXIMUM LINKS is 32. 3 MAXIMUM_PATH_SPLITS number<Indicates the maximum number of equal cost paths to a given ?destination node among which the packet load may be split. The*default is 1. The range is from 1 to 31.3 MAXIMUM_VISITS numberBSpecifies the maximum number of nodes a message can visit prior toEbeing received by the destination node. Use a numbe r in the range ofBMAXIMUM HOPS parameter to 63. You should specify a number that is1twice the MAXIMUM HOPS value. The default is 63.4 3 NAME node-name ESpecifies the node name to be associated with the executor node. YouBcan assign only one name to a node address or node identification.3 NODEFUse the SET EXECUTOR NODE command to set the default executor for allFNCP commands. The executor is the node on which the Net workCManagement Listener (NML) runs to perform these commands. (Do not8use the TELL prefix with the SET EXECUTOR NODE command.)FNote that the NODE keyword must appear as the third keyword whenFentering the command. The remaining information may appear in anyForder thereafter, except the node-spec which must follow the NODE1keyword. Access control information is optional. ?SET EXECUTOR NODE node-spec ACCOUNT accountA   PASSWORD password< USER user-id@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 4 ACCOUNT account>Identifies the user's account for access control verification at the designated executor node.4 NODE node-spec?Specifies a node name or address optionally followed by access =control information as specified for OpenVMS. Use one of thefollowing !formats: node-id" node-id"user password account"4 PASSWORD password?Identifies the user's password for access control verification at the designated executor node.4 USER user-id@Identifies the user's ID for access control verification at the designated executor node. 4 Examples NCP>SET EXECUTOR NODE 14 NCP>CLEAR EXECUTOR NODEA The first command sets the executor to node 1.14. (The @ default area number 1 is assumed if the area numb"er is @ not specified in the node address, and your network is ? not composed of multiple areas.) The second command / resets the executor to the local node.. NCP>SET EXECUTOR NODE 2.14"JOHNSON MYPWD"@ This command uses access control information to set the$ executor node to node 2.14.< NCP>SET EXECUTOR NODE TRNTO USER JOHNSON PASSWORD MYPWDB This command uses an alternate access control format to ( set the executor #to node TRNTO.. $ DEFINE NODE$MY TRNTO"""JOHNSON MYPWD""" $ RUN SYS$SYSTEM:NCP" NCP>SET EXECUTOR NODE NODE$MY@ The first command defines a logical name (NODE$MY) for = the given node-spec. When running NCP, you can use @ this logical name with the SET EXECUTOR NODE command. > Note that you must use three sets of quotation marks = to delimit access control information (if supplied)  in the node-spec.3 NONPRIVILEGED it $emBSpecifies nonprivileged inbound access control information for the,node. The following items can be specified:CACCOUNT account Identifies the account for default nonprivileged7 DECnet account on the executor node. DPASSWORD password Identifies the password for default nonprivileged7 DECnet account on the executor node. EUSER user-id Identifies the user name for default nonprivileged7 % DECnet account on the executor node. 3 OUTGOING_PROXY option=Indicates whether proxy login may be used on outgoing connect3requests. There are two options for OUTGOING PROXY:< DISABLED Specifies that proxy invocation is not requested* on any outgoing logical links. ; ENABLED Specifies that proxy invocation is requested on9 all outgoing logical links. This is default.3 OUTGOING_TIMER secondsDSpec &ifies a time out value for the elapsed time between the moment aFconnection is requested and the moment that connection is acknowledgedEby the destination node. A value in the range of 30 to 60 seconds is0recommended. The default is 60. 0 3 PATH SPLIT POLICY policyFSpecifies the policy for equal cost load splitting of network traffic.+There are two values for PATH SPLIT POLICY:? INTERIM Specifies that all traffic will 'be split over all? equal cost paths while forcing individual network@ sessions over the same paths in order to guarantee> that packets will be received by the destinationB node in the correct order. The INTERIM value should? be set if some of the nodes in the network do not@ support out-of-order packet caching. (VMS version: 4.5 and earlier VMS releases do not support $ out-of-order cac (hing.)@ NORMAL Specifies that all traffic will be split equally > over all equal cost paths to a destination node.> All destination nodes must support out-of-order B packet caching (supported by DECnet-VAX Version 4.6 F or higher); otherwise, network performance may suffer. > This is the default value for PATH SPLIT POLICY. 3 PIPELINE QUOTA quotaBSpecifies the maximum number of bytes of nonpaged pool that DECnetF )will use for transmission over logical links. Use this parameter forCbuffering at the NSP level. For satellite communications, a value /of 6000 or greater is recommended. 3 PRIVILEGED itemFSpecifies privileged inbound access control information for the node. %The following items can be specified:@ACCOUNT account Identifies the account for default privileged7 DECnet account on the executor node. APASSWORD password Identif *ies the password for default privileged7 DECnet account on the executor node. BUSER user-id Identifies the user name for default privileged7 DECnet account on the executor node. 3 RETRANSMIT FACTOR numberDDefines the maximum number of times any given message (except aBconnect initiate message) will be retransmitted before the logical/link is disconnected. The default value is 10.3 ROUTIN +G TIMER seconds DSpecifies the maximum amount of elapsed time before a routing updateCis forced on non-broadcast circuits. The routing update produces aDrouting configuration message for each adjacent node. You can use a>number in the range of 1 to 65535. The default value is 600. 3 SEGMENT BUFFER SIZE numberBSpecifies in bytes the maximum number of transmit buffers, thereby=controlling the maximum size NSP message segment that can be =transmitted. ,(This value is the maximum size message the EndFCommunication layer can transmit; it does not include Routing layer orFData Link layer overhead.) The default value is equal to the value of;the BUFFER SIZE if specified; otherwise the default is 576.CThe value of the SEGMENT BUFFER SIZE parameter must be less than orDequal to the value of the BUFFER SIZE parameter. The two values areDnormally equal but may differ to permit the network manager to alterCbuffer size on all nodes without inter-ruption of service. Refer toEthe DECnet for OpenVMS Networking Manual for information about how tomodify buffer sizes.  3 STATE node-stateBSpecifies the operational state of the local node. There are fourpossible states: @ OFF Allows no new logical links, terminates existing 6 links, and stops route-through traffic.$ ON Allows logical links.< RESTRICTED Allows no new inbound links fro.m other nodes.= SHUT Allows no new logical links, does not destroy > existing links, and goes to the OFF state when 2 all logical links are disconnected.3 SUBADDRESS range =Applies only to DLM circuits. Specifies a range of local DTECsubaddresses that the Routing Layer will accept as X.25 DLM calls. BVAX P.S.I. will route all incoming X.25 calls within the specifiedBsubaddress range to the Routing Layer to be handled as DLM calls. 3 TYPE nod/e-typeBIndicates the type of the executor node. Possible node types are: ROUTING IV NONROUTING IV AREADA ROUTING IV node has full routing capability. A NONROUTING IV nodeC(or end node) can deliver packets to or receive them from any node,;but cannot route packets from other source nodes through todestination nodes. FAn AREA node is a level 2 router that can route packets within its ownarea and between areas. 3 Examples NCP>SET EXECUTOR 0ALL; This command loads all permanent database entries > stored for the local node into the volatile database.# NCP>SET EXECUTOR ADDRESS 2.11 A This command sets the executor node's address to 2.11. ; (The executor must be in the OFF state to set the  ADDRESS parameter.) NCP>SET EXECUTOR STATE ONA This command sets the executor node's operational state  to ON.! NCP>SET NODE 2.13 NAME BIRDY& NCP>S 1ET EXECUTOR ALIAS NODE BIRDYC The SET NODE command establishes a node address 2.13 with A the associated node name BIRDY. The SET EXECUTOR ALIAS B NODE command then establishes the node name BIRDY as the B alias node identifier. (The executor must be in the OFF 0 state to set the ALIAS NODE parameter.), NCP>SET EXECUTOR ALIAS INCOMING ENABLED? This command specifies that incoming connect requests = directed to the alias nod2e identifier are permitted.# NCP>DEFINE EXECUTOR NAME ROBIN@ This command defines the executor node's name to ROBIN # in the permanent database.! 2 PROXIESEThe SET KNOWN PROXIES ALL command clears the contents of the volatileIproxy database and rebuilds the volatile proxy database from the contents of the permanent proxy database./ SET KNOWN PROXIES ALL! 2 LINE CUse the SET LINE command to create o 3r modify line parameters in theGvolatile database on the executor node. Most parameters cannot be SETHwhen the line is in the ON state. However, the COUNTER TIMER, STATE and<SERVICE TIMER parameters can be changed when the line is ON. (SET KNOWN LINES (parameters ...) LINE line-idFUse the DEFINE LINE command to create or modify line parameters in theDpermanent database on the executor node.  (DEFINE KN4OWN LINES (parameters ...) LINE line-idEAll underscores found in parameters must be replaced with spaces when$parameters are used in NCP commands. 3 ALL@Use the SET LINE ALL command to update the volatile copy of the@database on the executor node with all the line parameters=stored for a particular line in the permanent database on theexecutor node.3 BUFFER SIZE numberFSpecifies in bytes the size of receive buffers for the specified line,Fthereby controll5ing the maximum size of NSP message segments that can Ebe received from or forwarded to an adjacent node which has accepted Athe line buffer size. Use a value up to 65,535 for non-broadcastClines. For broadcast lines, BUFFER SIZE should not be raised to aFvalue higher than 1498 bytes. For Ethernet and FDDI lines, the valueAof 1498 bytes is provided as the default. For all other types ofFlines, the default is the executor BUFFER SIZE value (as specified inthe SET EXECUTOR command). 6 ,This parameter does not apply to X.25 lines.@You can use BUFFER SIZE to increase the size of NSP messages forlogical links over this line. 3 CLOCK clock-modeFApplies only to synchronous DDCMP lines. Specifies the hardware clockNmode for the line. The values for clock-mode are:  F INTERNAL For use of the clock in test mode. Setting this valueE causes the line device to supply a clock signal that E 7 will allow all transmitted messages to be looped backD from outside the device. Note that in order to use C this parameter, the operator may have to connect a : loopback plug in place of the normal line.F EXTERNAL For normal clock operating mode. The clock signal is 6 supplied externally to the controller.3 CONTROLLER modeBSpecifies the controller mode for the line. There are two possiblemodes: ELOOP8BACK Internal device loopback mode. Note that not all devices support this mode.8NORMAL Normal operating mode, which is the default.3 COUNTER TIMER seconds@Specifies a timer whose expiration causes a line counter logging<event. Specify a decimal integer up to a maximum of 65,535.3 DEAD TIMER milliseconds=Applies only to DDCMP CONTROL lines. Specifies the number ofCmilliseconds between polls of one of the set of dead tributaries. AThe milliseconds value9 must be a decimal integer up to a maximum .of 65,535. The default is 10000 (10 seconds).& 3 DELAY TIMER millisecondsDApplies only to DDCMP CONTROL lines. Specifies the minimum number ofEmilliseconds to delay between polls. This timer limits the effect ofDa very fast control station to slower tributaries. The millisecondsBvalue must be a decimal integer up to a maximum of 65,535. If notset, there is no delay.  3 DUPLEXBApplies to DDCMP: lines. Specifies the hardware duplex mode of the*line. There are two possible modes:  HALF Half-duplex" FULL Full-duplex (default)3 ECHO_DATA hex_byteAApplies only to FDDI lines. Specifies the byte consisting of twoFhexadecimal digits used as data in an echo request frame. The size ofFthe frame is determined by the ECHO LENGTH parater. The frame is sent8to the address specified by the ECHO TARGET parameter. AHex_byte must be a string of exactly two hexad ;ecimal digits. The>default ECHO DATA is 55. ECHO DATA can be set in the volatile=database, but it cannot be defined in the permanent database. 3 ECHO_LENGTH numberEApplies only to FDDI lines. Specifies the number of bytes used in anDecho request frame. The hexadecimal bytes are specified by the ECHOFDATA parameter. The frame is sent to the address specified by the ECHOTARGET parameter. DThe number must be a decimal value from 0 to 4478. The default ECHOFLENGTH is < 1. ECHO LENGTH can be set in the volatile database, but it,cannot be defined in the permanent database. 3 ECHO TARGET p-addressDApplies only to FDDI lines. Specifies the address to which the next:echo request frame will be sent. The default ECHO TARGET Ais 00-00-00-00-00-00. The ECHO TARGET can be set in the volatile=database, but it cannot be defined in the permanent database. 3 HANGUP optionFApplies only to asynchronous DDCMP lines. Indicates whe =ther the modemEsignals are dropped when the line is shut down. Possible values are:" E ENABLED Indicates that modem signals should be dropped when ' the line is shut down.C DISABLED Indicates that modem signals should not be droppedE when the line is shut down. This is the default for1 static asynchronous DDCMP lines.AThis parameter is supplied automatically for dynamic asynchronousDDD >CMP lines. The default is HANGUP ENABLED if the /HANGUP qualifierDwas specified for the DCL command SET TERMINAL, and HANGUP DISABLED #if /NOHANGUP was specified. 3 HOLDBACK TIMER millisecondsDApplies only to X.25 lines. Specifies the maximum delay before thisEX.25 software acknowledges successful receipt of data. If you do notEspecify this parameter, then the acknowledgment is sent immediately. ?If you specify a holdback timer, performance may be improved byAallowing the a?cknowledgment to be included with a subsequent dataDmessage transmitted. This parameter cannot be set to a value larger:than one half the value of the RETRANSMIT TIMER parameter.3 INTERFACE codeFApplies only to X.25 lines and the ISO8208 profile. Specifies the way Ain which the processor acts when it uses the line. There are two values for the code:9 DTE Specifies that the processor operates as a DTE. 8 DCE Specifies that the processor operates as a DCE.The default co@de is DTE. 3 KNOWN LINES;Indicates that the specified parameters for all known lines.are to be created or modified in the database.3 LINE line-id<Identifies the line for which specified parameters are to be$created or modified in the database.3 LINE SPEED speedEApplies only to asynchronous DDCMP lines. Specifies the speed of theCline in baud. This parameter must be set to the same value on both=sides of the asynchronous DDCMP connection. It is specifiedFautomatically for Adynamic asynchronous DDCMP lines. If not specified,Fthe vlaue of this parameter is equal to the current speed of the line.3 MAXIMUM_BLOCK numberDApplies only to X.25 lines. Specifies the maximum size in bytes of Dthe frame for the line. This value must be at least 5 bytes larger Fthan the maximum packet size you specify in SET CIRCUIT (for PVCs and FDLM circuits) or SET MODULE X25-PROTOCOL (for SVCs) command. Specify a value in the range 21 to 4103.BBy default the size of the frame B takes the value specified by the BPROFILE parameter of the SET MODULE X25-PROTOCOL command. See the=Public Network Information manual for a network value of this parameter.3 MAXIMUM_RETRANSMITS number <Applies only to X.25 lines. Specifies the maximum number ofDretransmissions of a frame on the specified line. Specify a value inCthe range 1 to 255. By default, the retransmission value takes theBnetwork value specified by the NETWORK parameter of the SET MODULEDX25-PROTOCOL command C. See the Public Network Information manual for$the network value of this parameter. 3 MAXIMUM_WINDOW numberCApplies only to X.25 lines. Specifies the maximum number of framesFfor which outstanding acknowledgments are allowed. Specify a value up=to a maximum of 127. By default window size takes the value?specified by the PROFILE parameter of the SET or DEFINE MODULEDX25-PROTOCOL command. See the Public Network Information manual for$the network value of tDhis parameter. 3 MICROCODE DUMP file-specAApplies only to X.25 lines. Dumps the microcode of the specified EKMS-11, KMS1P, or KMV1A device to the indicated file. By default, theoutput file takes the format:SYS$ERRORLOG:file-id.DMPBThe KMS/KMV Dump analyzer (PSIKDA) is the utility program used to Eprocess the dump file created by the MICROCODE DUMP parameter. ReferBto the VAX P.S.I. Problem Solving Guide for more information aboutPSIKDA.3 NETWORK ne Et-nameGApplies only to X.25 lines. Specifies the network to which the line is Gconnected. If only one network is set up, that network is the default. -Otherwise the NETWORK parameter is mandatory.3 NIF TARGET p-addressEApplies only to FDDI lines. Specifies the address to which the next ENeighborhood Information Frame (NIF) request frame will be sent. TheBdefault NIF target is 00-00-00-00-00-00. NIF TARGET can be set in@the volatile database, but it cannot be defined in the permaFnent database. 3 PROTOCOL protocol-name>Specifies the Data Link protocol to be used on this line. The/following values can be used for protocol-name: GDDCMP CONTROL Specifies this line as a multipoint control station. F You can specify multiple circuits for CONTROL lines, > but each circuit must have a unique physical # tributary address.DDDCMP DMC Specifies that this line is i Gn DMC emulator mode. B DMC is similar to POINT, except that DMC uses an F older version of DDCMP (Version 3.2). This protocol B should be set for the local line when the remote B line is a DMC. Note that this protocol is valid : only when a DMP11 or DMV11 is being used. EDDCMP POINT Specifies this line as one of a point-to-point DDCMPC connection. You can specify only one circuit per  H POINT line.BDDCMP TRIBUTARY Specifies that this line is a tributary end of a C DDCMP multipoint group. You may specify only one - circuit per TRIBUTARY line. EETHERNET Specifies that this line uses the Ethernet protocol.AFDDI Specifies that this line uses the FDDI protocol.@LAPB Specifies that this line uses the X.25 level 2 < protocol. The line must be a line for the & I X25-PROTOCOL module. @LAPBE Specifies that this line uses the X.25 level 2 F protocol with extended sequencing. The line must be 1 used by the X25-PROTOCOL module.DDefault line protocols are based on line names. See HELP PARAMETERS3DEVICE-TYPE for a list of circuit and line devices.7 3 RECEIVE BUFFERS numberFSpecifies the length of the line's receive queue. Use a number in the rangJe of 1 to 32. 3 REQUESTED TRT microsecondsCApplies only to FDDI lines. Specifies the requested value for theEtoken rotation timer in microseconds. Microseconds must be a decimal<integer in the range of 4000 to 167772. The default is 8000 microseconds.(3 RESTRICTED TOKEN TIMEOUT milliseconds GApplies only to FDDI lines. Specifies the limit on how long a single Frestricted mode dialog may last before being terminated. Milliseconds Dmust be a decimal integer in the range of K0 to 10000. The default is 1000 milliseconds.3 RETRANSMIT TIMER millisecondsCApplies only to DDCMP and X.25 lines. For a DDCMP multipoint line,@specifies the maximum amount of time allowed to elapse before aCretransmission is necessary. This is the amount of time a controlFstation will wait for a tributary to respond. Milliseconds must be aBdecimal integer in the range 1 to 65535. The default value is thenetwork default.3 RING PURGER ENABLE option3Applies only to FDDI L lines. The option values are:7 ON Participate in the Ring Purger election and, 9 if elected, perform the Ring Purger function.  This is the default.: OFF Do not participate in the Ring Purger election. FThis parameter is to allow operation when stations on your ring do notFconform to the FDDI specification. Except for that case, it should be&left ON for improved ring reliability.1 3 SCHEDULING TIMER m Milliseconds=Applies only to DDCMP CONTROL lines. Specifies the number ofEmilliseconds between re-calculation of tributary polling priorities. DThe number of milliseconds must be a decimal integer up to a maximumof 65,535. The default is 50. C 3 SERVICE TIMER millisecondsCDoes not apply to X.25 lines. Specifies the maximum amount of timeEallowed to elapse before a receive request completes while performingEservic Ne operations on a line. Milliseconds must be a decimal integerDfrom 1 to 65,535. The default value is 4000 (4 seconds). %3 SIF_CONFIGURATION_TARGET p-address AApplies only to FDDI lines. Specifies the address to which the aBStatus Information Frame (SIF) configuration request frame will beDsent. The default SIF configuration target is 00-00-00-00-00-00. DSIF CONFIGURATION TARGET can be set in the volatile database, but it,cannot be defined in the permanent database. 3 OSIF_OPERATION_TARGET p-addressDApplies only to FDDI lines. Specifies the address to which a StatusBInformation Frame (SIF) operation request frame will be sent. TheAdefault SIF operation target is 00-00-00-00-00-00. SIF OPERATIONDTARGET can be set in the volatile database, but it cannot be definedin the permanent database.3 STATE line-stateFSpecifies the line's operational state. There are three possible linestates: $ OFF The line is not in use.2 ON P The line is available for normal use.> SERVICE The line is available only for service functions.3 STREAM TIMER milliseconds=Applies only to DDCMP CONTROL lines. Specifies the number ofDmilliseconds a tributary or half duplex remote station is allowed toDhold the line. The number of milliseconds must be a decimal integerGup to a maximum of 65,535. The default is 1000 (1 second).  3 SWITCH optionBApplies only to asynchronous DDCMP lines. Resets a line c QurrentlyAbeing used as a DECnet asynchronous communications line back to a1terminal line. The two values of the option are:5 A ENABLED The line is switched to a terminal line after it is D disconnected from the network (when the channel to the > network is deassigned). This is the default for  dynamic lines.C DISABLED The line is not switched to a terminal line. This is * the R default for static lines. 3 TRANSMIT PIPELINE numberCApplies only to DMR11 lines. Specifies the maximum number of DDCMPFmessages for which outstanding acknowledgments are allowed. Specify aBvalue in the range 1 to 32. By default, the value for outstandingEDDCMP messages is 7. To avoid excessive use of system memory, do notFarbitrarily set this value higher than necessary. Refer to the DECnetBfor OpenVMS Networking Manual for the procedure for determining an optimum TRANSMIT PIPSELINE value.&3 VALID TRANSMISSION TIME microseconds@Applies only to FDDI lines. Specifies the maximum time between Carrivals of a valid frame or unrestricted token. Microseconds must@be a decimal integer in the range of 2500 to 5222. The default is 2621 microseconds. 3 Examples NCP>SET KNOWN LINES ALLB This command loads all permanent database entries stored 8 for all known lines into the volatile database., NCP>SET LINE DMC-0 DUPLEX FTULL STATE ON> This command sets line DMC-0 to the ON state in full  duplex mode.0 NCP>DEFINE LINE DMC-0 PROTOCOL DDCMP POINT ? This command defines the line protocol to DDCMP POINT 2 for line DMC-0 in the permanent database.6 NCP>SET LINE DUP-1 RETRANSMIT TIMER 500 MAXIMUM -> _ RETRANSMITS MAXIMUM BLOCK 133 MAXIMUM WINDOW 2 STATE ON@ This command sets up a line called DUP-1 that uses the B LAPB protocol and has an associ Uated DUP11-DA synchronous A line interface with controller number 1. If a frame is 9 not acknowledged within 500 milliseconds, it is @ retransmitted, and this operation is to be performed a = maximum of 10 times. The maximum frame size is 133 ; bytes, and the maximum number of frames for which A outstanding acknowledgments are allowed is 2. The line  is operational.. NCP>SET LINE KMX-0-0 MICROCODE DUMP BARRY@ ThiVs command dumps the microcode of the KMX to the file SYS$ERRORLOG:BARRY.DMP., NCP>SET LINE KMV-0 NETWORK PSS STATE ON@ This command sets up the line KMV-0 to the PSS network.+ NCP>SET LINE DMF-* CONTROLLER LOOPBACKB This command sets the controller mode to loopback for all DMF lines.! 2 LOGGINGIUse the SET LOGGING command to create or modify logging parameters in theEvolatile database. Use the DEFINE LOGGING command to create or mod Wify.logging parameters in the permanent database.  SET KNOWN LOGGING ALL+DEFINE LOGGING CONSOLE NAME prog-name& LOGGING FILE STATE ON' LOGGING MONITOR OFF( HOLDHThe CIRCUIT, LINE, and NODE parameters in the following commands are forBidentifying specific sources of events. The SINK parameter is forDidentifying specific locations to log events. These source and sinkparameters are optXional. ESET KNOWN LOGGING EVENTS event-list CIRCUIT circuit-id ?DEFINE LOGGING CONSOLE KNOWN EVENTS LINE line-id > LOGGING FILE NODE node-idA LOGGING MONITOR SINK EXECUTORE NODE node-idEAll underscores found in parameters must be replaced with spaces when$parameters are used in NCP commands. 3 ALL?Indicates that all log Yging parameters for the specified logging>components (CONSOLE, FILE, or MONITOR) are to be added to the database.  3 CIRCUIT circuit-idAIdentifies the circuit to which the events apply. Events will be;logged for this source. This parameter can only be used in7conjunction with the EVENTS or KNOWN EVENTS parameters.B 3 CONSOLECIndicates that the parameters for logging to the console are Z to be =added to the database. The default logging console is OPA0:.3 EVENTS event-listGIdentifies the class and types of events to be added to the database. -See HELP EVENTS for a list of valid events.  DThe EVENTS event-list parameter may be followed by a specific sourceFfor events (using the CIRCUIT, LINE, or NODE parameters) or a specificClocation for logging these events (using the SINK parameter). Only0one source or sink can be specified per comm[and. 3 FILE7Indicates that the parameters for logging to a file are4to be added to the database. 3 KNOWN_EVENTSDIndicates that all events are to be logged to the specified logging%component or components. CThe KNOWN EVENTS parameter may be followed by a specific source forBevents (using the CIRCUIT, LINE, or NODE parameters) or a specificClocation for logging these events (using the SINK parameter). Only0one source or sink\ can be specified per command. 3 KNOWN_LOGGING=Indicates that the specified parameters for all known logging>components (CONSOLE, FILE, and MONITOR) are to be added to the database.3 LINE line-idEIdentifies the line to which the events apply. Events will be loggedEfor this source. This parameter can only be used in conjunction with&the EVENTS or KNOWN EVENTS parameters. 3 MONITORFIndicates that the parameters for logging to a monitor program are to @be ] added to the database. The default logging monitor is OPCOM.3 NAME prog-nameCIdentifies the name of a console, file, or monitor program to whichFevents will be logged. The logging component must be in the OFF stateFto SET the NAME parameter. If NAME parameter is not specified for theEmonitor sink, events will be sent to the default monitor, OPCOM. IfDNAME parameter is not specified for the console sink, events will besent to OPA0:.* 3 NO^DE node-idEIdentifies the node to which the events apply. Events will be loggedEfor this source. This parameter can only be used in conjunction with&the EVENTS or KNOWN EVENTS parameters.A 3 SINK sink-name>Identifies the location where the events will be logged. ThisCparameter can only be used in conjunction with the EVENTS or KNOWN 8EVENTS parameters. There are two possible sink-names:  ANODE nod _e-id Identifies the node at which events to be logged.-EXECUTOR Identifies the executor node.DIf this parameter is omitted, the executor node is assumed to be theJsink node affected. 3 STATE component-stateESpecifies the operational state of the logging component or all known>logging components. There are three possible component states:D F HOLD Th`e logging component is temporarily unavailable and events  should be queued.D OFF The logging component is unavailable for receiving events.B ON The logging component is available for receiving events. 3 Examples) NCP>SET LOGGING MONITOR KNOWN EVENTS% NCP>SET LOGGING MONITOR STATE OND These two commands enable normal event logging using OPCOM.C To receive the formatted events at a terminal, use the DCL& command REPLY/ENABLE=NEaTWORK.7 NCP>DEFINE LOGGING MONITOR LINE FZA-1 KNOWN EVENTSB This command defines logging so that all events for line C FZA-1 will be logged to the logging monitor the next time  DECnet is restarted.8 NCP>SET LOGGING CONSOLE EVENTS 4.* SINK NODE LAMCHPC This command causes all class 4 events to be logged on the+ console of the remote node LAMCHP.' NCP>SET LOGGING MONITOR EVENTS 7.*D This command causes all X.25-relabted events to be logged to$ OPCOM, the default monitor. NCP>SET KNOWN LOGGING ALLE This command loads all permanent database entries stored for; all logging components into the volatile database. 2 MODULE 'Introduces the various module entities.3 CONFIGURATORC ?Use the SET MODULE CONFIGURATOR command to create or modify the?parameters of the Ethernet configurator module component in cthe@volatile database at the local node on an Ethernet circuit. TheEDEFINE MODULE CONFIGURATOR command creates or modifies the parametersDof the configurator module component in the permanent database. YouFmust specify a qualifier following the CONFIGURATOR command verb. BThe configurator module constructs a list of systems active on the)Ethernet circuit or circuits specified.  2SET MOD CONFIGURATOR KNOWN CIRCUITS ALLCDEFINE CIRCUIdT circuit-id SURVEILLANCE control@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 4 ALLFCopies the configurator module information from the permanent database-into the volatile database at the local node.4 CIRCUIT circuit-id?Applies only to Ethernet circuits. Specifies that configuratorFinformation on the identified circuit is to be stored in the database. 4 KNOWN CIRCUITSDSpecifeies that configutor information on all known Ethernet circuits is to be stored in the database. 4 SURVEILLANCE controlCIndicates whether or not a list of active systems is to be kept forBthe Ethernet circuit or circuits specified. There are two controlvalues: < DISABLED The list is not to be kept. This is the default.# ENABLED The list is to be kept. 4 ExamplesD NCP>SET MODULE CONFIGURATOR KNOWN CIRCUITS SURVEILLANCE ENABLEDD f This command specifies that a list of active systems on all/ known Ethernet circuits is to be kept.< NCP>SET CONFIGURATOR CIRCUIT MNA-0 SURVEILLANCE ENABLEDA This command specifies that a list of active systems on . Ethernet circuit MNA-0 is to be kept.3 NCP>SET MODULE CONFIGURATOR KNOWN CIRCUITS ALLC This command loads all permanent database entries for the 8 configurator module into the volatile database. 3 X25-ACCESS FUse th ge SET MODULE X25-ACCESS and DEFINE MODULE X25-ACCESS commands toDassociate the host node with the specified multi-host connector nodeEfor the purpose of accessing a specified X.25 network. The multi-hostDnode connected to the specified X.25 network is an OpenVMS VAX node .with VAX P.S.I. multi-host software installed. 2SET MODULE X25-ACCESS NETWORK net-name ALL>DEFINE KNOWN NETWORKS ACCOUNT account; NODE nodeh-id@ PASSWORD password; USER user-id@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 4 ACCOUNT account:Identifies the user account for use when connecting to the;multihost connector node. Specify a string of from 1 to 39-characters. By default, no account is used. 8 4 ALL i=Copies all X25-ACCESS parameters from the permanent data base>into the volatile data base. Use this parameter only with theGSET MODULE X25-ACCESS command. 4 KNOWN NETWORKS Identifies all known networks. 4 NETWORK net-name AIdentifies the network whose parameters are to be set in the database. 4 NODE node-id ASpecifies the multihost connector node connected to the PSDN that?you want to access. When you specify an X25-ACCESjS network forBthe first time, this parameter is mandatory. 4 PASSWORD password:Specifies the password for use by the access routines when>connecting to a multihost connector node. Specify a string of=from 1 to 39 characters. The default is that no password isused. 4 USER user-id@Specifies the user identification for use by the access routines@in connecting to the multihost connector node. Specify a string9of from 1 to 16 characters. The kdefault is that no useridentification is used.! ;4 Examples 9 NCP>SET MODULE X25-ACCESS NETWORK TELENET1 NODE FRED7 NCP>SET MODULE X25-ACCESS NETWORK PSS1 NODE GINGERB These two commands allow users on the host node to access@ the network called TELENET1 through node FRED, and the 1 network called PSS1 through node GINGER.1 NCP>SET MODULE X25-ACCESS KNOWN NETWORKS lALLA This command loads all permanent database entries stored@ for the X25-ACCESS database into the volatile database.! 3 X25-PROTOCOL?Use the SET MODULE X25-PROTOCOL command to create or modify theFparameters of the Protocol Module component in the volatile data base.BUse the DEFINE MODULE X25-PROTOCOL command to create or modify theAparameters of the Protocol Module component in the permanent database. FUse separate SET MODULE X25-PROTOCOL commands to a spe mcify a DTE with Gits associated parameters, a group with its associated parameters, and Dthe network profile. The X25-PROTOCOL module contains records that ?identify the packet switching data networks (PSDNs) your DTE isBconnected to, associate your local DTE (and possibly a group name)5with VAX P.S.I., and control transmission of packets. CSET MOD X25-PROTOCOL DTE dte-addr NETWORK net-name dte-params5DEFINE KNOWN DTES KNOWN NETWORKS/SET MOD X25-PRO nTOCOL GROUP group-name ALL8DEFINE KNOWN GROUPS DTE dte-addr< NETWORK net-name? NUMBER group-number: TYPE BILATERAL@SET MOD X25-PROTOCOL NETWORK net-name PROFILE profile-name/DEFINE KNOWN NETWORKS ALL@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. o 4 DTE_dte-addrBIdentifies a local DTE. See the Public Network Information manual $for the format of the DTE address. ASET MOD X25-PROTOCOL DTE dte-addr NETWORK net-name dte-params3DEF KNOWN NETWORKS@If you have only one network set up, that network is the defaultAfor SET commands. If you have more than one network set up or ifAyou are using a DEFINE command, then you must specify the network9using either the NETWORK parameterp or the KNOWN NETWORKS Aparameter. In any case, you must follow the DTE qualifiers with )one or more of the following dte-params. * 5 ALL:Copies DTE parameters from the permanent database into the>volatile database. Use this parameter only with the SET MODULEX25-PROTOCOL command.@ 5 CALL TIMER seconds @Specifies a timer that starts when a request to set up a virtual?circuit qis transmitted, and whose expiration clears the request@if no response has been received. Specify a value in the range 1?to 255. By default, the timer takes the network value specified=by the NETWORK parameter. See the Public Network Information0manual for the network value of this parameter. 5 CHANNELS list?Specifies a list of logical channel numbers (LCNs) reserved for:outgoing calls. The list can consist of one or more LCNs.ASeparate multiple channel numbers with hyp rhens to indicate ranges@and with commas to indicate individual numbers. Specify a value:in the range 0 to 4095 for each LCN. If a DTE is to make>outgoing calls, this parameter is mandatory when you specify a?DTE for the first time. The LCN range at the DTE is defined by&PSDN authorities at subscription time.5 CLEAR TIMER seconds=Specifies a timer that starts when a request to clear an X.25Avirtual circuit is transmitted, and whose termination retransmits>the clear request if no sresponse has been received. Specify a>value in the range 1 to 255. By default, the timer takes theAnetwork value specified by the PROFILE parameter. See the Public9Network Information manual for the network value of this parameter. 5 COUNTER TIMER secondsBSets a timer whose expiration causes a DTE counter logging event. 3Specify a decimal integer in the range 1 to 65,535.5 DEFAULT_DATA bytesBSpecifies the default packet size for X.25 virtual circuits. This @va tlue must be at least 5 bytes less than the MAXIMUM BLOCK value>you specify in the SET LINE command and must be a power of 2.;Specify a value in the range 16 to 4096 bytes. By default=packet size takes the network value specified by the PROFILE=parameter. See the Public Network Information manual for the!network value of this parameter. 5 DEFAULT_WINDOW numberASpecifies the default window size for X.25 virtual circuits, that8is, the maximum number of packets for w uhich outstanding=acknowledgments are allowed. Specify a value in the range 1 8to 127. By default, window size takes the network value<specified by the PROFILE parameter. See the Public Network<Information manual for the network value of this parameter. 0 5 INTERFACE codeASpecifies the way in which the processor operates. This parameter=can only be used with the ISO8208 profile. The parameter can"take one of the followingv values:.DTE The processor operates as a DTE..DCE The processor operates as a DCE.@NEGOTIATED The processor can operate either as a DTE or DCE. > The processor automatically selects the correct " method of operation.The default is DTE.5 INTERRUPT TIMER seconds@This is the interrupt timer (ISO T26 timer). This parameter can>only be used with the ISO8208 profile. Specify a value in the@range 1 to 255. If you do not specify a vwalue, there is no time#limit on interrupt acknowledgments. 5 LINE line-id@Identifies the line associated with the DTE. Specify a line name=in the format dev-c[-u]. This parameter is mandatory when you!specify a DTE for the first time.5 MAXIMUM_CIRCUITS countASpecifies the maximum number of circuits for the DTE. By default,:the count takes the network value specified by the PROFILE=parameter. See the Public Network Information manual for the network valuxe of this parameter.= 5 MAXIMUM_CLEARS countBSpecifies the maximum number of attempts to clear an X.25 virtual >circuit. Specify a value in the range 1 to 255. By default the?value is the network value specified by the PROFILE parameter. ?See the Public Network Information manual for the network valueof this parameter.= 5 MAXIMUM_DATA bytesBSpecifies the maxi ymum packet size for X.25 virtual circuits. This @value must be at least 5 bytes less than the MAXIMUM BLOCK value=you specify in the SET LINE command and must be a power of 2.>Specify a value in the range 16 to 4096 bytes. By default the9value taken is the network value specified by the PROFILE=parameter. See the Public Network Information manual for the network value of this parameter.=  5 MAXIMUM_RESETS z countASpecifies the maximum number of attempts to reset an X.25 virtualAcircuit. If this number is exceeded, the virtual circuit will beAcleared. Specify a value in the range 1 to 255. By default, theBcount takes the network value specified by the PROFILE parameter. ?See the Public Network Information manual for the network valueof this parameter. 5 MAXIMUM_RESTARTS count;Specifies the maximum number of attempts to restart an X.25<virtual circuit. Specify a valu {e in the range 1 to 255. By;default, the count takes the network value specified by the>PROFILE parameter. See the Public Network Information manual (for the network value of this parameter.= 5 MAXIMUM_WINDOW count=Specifies the window size allowed for X.25 virtual circuits, <that is, the maximum number of packets for which outstanding<acknowledgments are allowed. Specify a value in the range 1 <to 127. By default, the win |dow size takes the network value;specified by the PROFILE parameter. See the Public Network;Information manual for the network value of this parameter.= 5 RESET TIMER seconds>Specifies a timer that starts when a reset is transmitted, and?whose termination retransmits the reset if no response has been@received. Specify a value in the range 1 to 255. By default theBtimer takes the network value specified by the PROFILE param }eter. ?See the Public Network Information manual for the network valueof this parameter.5 RESTART TIMER seconds@Specifies a timer that starts when a restart is transmitted, and<whose termination retransmits the restart if no response has:been received. Specify a value in the range 1 to 255. By;default, the timer takes the network value specified by the>PROFILE parameter. See the Public Network Information manual(for the network value of this parameter.= ~  5 STATE dte-state6Specifies the operational state of the DTE as follows:, ON The DTE is available for normal use.: OFF The DTE is not in use. This is the default state.9 SHUT The DTE is to be closed down and a reset is sent.: Use only with the SET MODULE X25-PROTOCOL command. !end of DTES4 GROUP_group_name=Identifies a closed user group (CUG) or bilateral closed usergroup (BCUG). /SET MOD X25-PROTOCOL GR OUP group-name ALL8DEFINE DTE dte-addr< NETWORK net-name? NUMBER group-number: TYPE BILATERALAEach group specified should have a unique group-name from 2 to 16?characters long. You must follow the GROUP qualifiers with one+or more of the following group parameters.  5 ALL ACopies the group parameters from the permanent data base into the?volatile data base. Used only with the SET MODULE X25-PROTOCOL command. 5 DTE dte-addr >Identifies the local DTE associated with the group name. This.parameter is mandatory when creating a group. 5 NETWORK net-name9Identifies a network to which the DTE is connected. This5parameter is mandatory when you are creating a group.5 NUMBER group-number @Specifies the CUG or BCUG number. Specify a two-digit number for?a CUG and a four-digit number for a BCUG. You can omit leading>zeroes. This parameter is mandatory when you are associating aDTE with a group. 5 TYPE BILATERAL >Specifies the user group as a BCUG. Omit this parameter if the>user group is a CUG. This parameter is mandatory when you areEassociating a DTE with a BCUG. !end of group parameters 4 KNOWN_DTESRefers to all known DTEs.?SET MOD X25-PROTOCOL KNOWN DTES NETWORK net-name dte-params1DEF  KNOWN NETWORKS@If you have only one network set up, that network is the defaultAfor SET commands. If you have more than one network set up or ifAyou are using a DEFINE command, then you must specify the network9using either the NETWORK parameter or the KNOWN NETWORKS Bparameter. In any case, you must follow the KNOWN DTES qualifier -with one or more of the following dte params. 5 ALL:Copies DTE parameters from the permanent database into the>volatile dat abase. Use this parameter only with the SET MODULEX25-PROTOCOL command.$ 5 CALL TIMER seconds @Specifies a timer that starts when a request to set up a virtual?circuit is transmitted, and whose expiration clears the request@if no response has been received. Specify a value in the range 1?to 255. By default, the timer takes the network value specified=by the NETWORK parameter. See the Public Network Information0manual for the network value of this parameter. 5 CHANNELS list?Specifies a list of logical channel numbers (LCNs) reserved for:outgoing calls. The list can consist of one or more LCNs.ASeparate multiple channel numbers with hyphens to indicate ranges@and with commas to indicate individual numbers. Specify a value:in the range 0 to 4095 for each LCN. If a DTE is to make>outgoing calls, this parameter is mandatory when you specify a?DTE for the first time. The LCN range at the DTE is defined by&PSDN authorities at subscription time.5 CLEAR TIMER seconds=Specifies a timer that starts when a request to clear an X.25Avirtual circuit is transmitted, and whose termination retransmits>the clear request if no response has been received. Specify a>value in the range 1 to 255. By default, the timer takes theAnetwork value specified by the PROFILE parameter. See the Public9Network Information manual for the network value of this parameter. 5 COUNTER TIMER secondsBSets  a timer whose expiration causes a DTE counter logging event. 3Specify a decimal integer in the range 1 to 65,535.5 DEFAULT_DATA bytesBSpecifies the default packet size for X.25 virtual circuits. This @value must be at least 5 bytes less than the MAXIMUM BLOCK value>you specify in the SET LINE command and must be a power of 2.;Specify a value in the range 16 to 4096 bytes. By default=packet size takes the network value specified by the PROFILE=parameter. See the Public Network Information manual for the!network value of this parameter. 5 DEFAULT_WINDOW numberASpecifies the default window size for X.25 virtual circuits, that7is, the maximum number of packets for which outstanding>acknowledgments are allowed. Specify a value in the range 1 8to 127. By default, window size takes the network value<specified by the PROFILE parameter. See the Public Network<Information manual for the network value of this parameter. 5 INTERFACE codeASpecifies the way in which the processor operates. This parameter=can only be used with the ISO8208 profile. The parameter can"take one of the following values: / DTE The processor operates as a DTE./ DCE The processor operates as a DCE.A NEGOTIATED The processor can operate either as a DTE or DCE. ? The processor automatically selects the correct # method of operation.The default is DTE.5 INTERRUPT TIMER seconds?This is the interrupt timer (ISO T26 timer). This parameter can>only be used with the ISO8208 profile. Specify a value in the?range 1 to 255. If you do not specify a value there is no time$limit on interrupt acknowledgments.5 LINE line-id@Identifies the line associated with the DTE. Specify a line name>in the format dev-c[-u]. This parameter is mandatory when you"specify a DTE for the first time.5 MAXIMUM_CIRCUITS countASpecifies the maximum number of circ uits for the DTE. By default,:the count takes the network value specified by the PROFILE=parameter. See the Public Network Information manual for the!network value of this parameter.= 5 MAXIMUM_CLEARS countBSpecifies the maximum number of attempts to clear an X.25 virtual >circuit. Specify a value in the range 1 to 255. By default the@value is the network value specified by the PROFILE parameter. ?See the Public Network I nformation manual for the network valueof this parameter.= 5 MAXIMUM_DATA bytesBSpecifies the maximum packet size for X.25 virtual circuits. This @value must be at least 5 bytes less than the MAXIMUM BLOCK value>you specify in the SET LINE command and must be a power of 2.?Specify a value in the range 16 to 4096 bytes. By default the:value taken is the network value specified by the PROFILE=parameter. See the Public Net work Information manual for the network value of this parameter.= 5 MAXIMUM_RESETS countASpecifies the maximum number of attempts to reset an X.25 virtualAcircuit. If this number is exceeded, the virtual circuit will beAcleared. Specify a value in the range 1 to 255. By default, theBcount takes the network value specified by the PROFILE parameter. ?See the Public Network Information manual for the network valueof this parameter.5 MAXIMUM_RESTARTS count;Specifies the maximum number of attempts to restart an X.25<virtual circuit. Specify a value in the range 1 to 255. By;default, the count takes the network value specified by theAPROFILE parameter. See the Public Network Information manual for$the network value of this parameter.= 5 MAXIMUM_WINDOW countASpecifies the window size allowed for X.25 virtual circuits, that7is, the maxi mum number of packets for which outstanding=acknowledgments are allowed. Specify a value in the range 1 <to 127. By default, the window size takes the network value;specified by the PROFILE parameter. See the Public Network;Information manual for the network value of this parameter.= 5 RESET TIMER seconds>Specifies a timer that starts when a reset is transmitted, and@whose termination retransmits the reset if no respons e has been@received. Specify a value in the range 1 to 255. By default theBtimer takes the network value specified by the PROFILE parameter. ?See the Public Network Information manual for the network valueof this parameter. 5 RESTART TIMER seconds@Specifies a timer that starts when a restart is transmitted, and=whose termination retransmits the restart if no response has:been received. Specify a value in the range 1 to 255. By;default, the timer takes the network value specified by the>PROFILE parameter. See the Public Network Information manual(for the network value of this parameter.= 5 STATE dte-state6Specifies the operational state of the DTE as follows:+ ON The DTE is available for normal use.9 OFF The DTE is not in use. This is the default state.8 SHUT The DTE is to be closed down and a reset is sent.9 Use only with the SET MODULE X25-PROTOCOL command. !end of DTES4 KNOWN_GROUPSSpecifies all known groups. .SET MODULE X25-PROTOCOL KNOWN GROUPS ALL7DEFINE DTE dte-addr; NETWORK net-name> NUMBER group-number9 TYPE BILATERALBEach group specified should have a unique group-name from 2 to 16 Acharacters long. You must follow the KNOWN GROUPS qualifier with4one or more of the following group parameters. 5 ALL ACopies the group parameters from the permanent data base into the?volatile data base. Used only with the SET MODULE X25-PROTOCOL,command. 5 DTE dte-addr >Identifies the local DTE associated with the group name. This.parameter is mandatory when creating a group. 5 NETWORK net-name9Identifies a network to which the DTE is connected. This5parameter is mandatory when you are creating a group. 5 NUMBER group-number @Specifies the CUG or BCUG number. Specify a two-digit number for?a CUG and a four-digit number for a BCUG. You can omit leading>zeroes. This parameter is mandatory when you are associating aDTE with a group. 5 TYPE BILATERAL >Specifies the user group as a BCUG. Omit this parameter if the>user group is a CUG. This parameter is mandatory when you areassociating a DTE with a BCUG. !end of group parameters4 KNOWN_NETWORKSAIdentifies all known networks. You must also specify the PROFILEor the ALL parameter. ?SET MODULE X25-PROTOCOL KNOWN NETWORKS PROFILE profile-name.DEFINE ALL5 ALL ?Copies the network parameters from the permanent data base into5the volatile data base. Use only with the SET MODULEX25-PROTOCOL command. 5 PROFILE profile-name?Specifies a profile to be used on the network. The profile-name@is a character string of up to 32 characters. This parameter isAmandatory. Refer to the Public Network Information manual for thevalid profile-name. 4 NETWORK_net-name?Identifies a network. You must also specify the PROFILE or theALL parameter.=SET MOD X25-PROTOCOL NETWORK net-name PROFILE profile-name,DEF ALL5 ALL ?Copies the network parameters from the permanent data base into5the volatile data base. Use only with the SET MODULEX25-PROTOCOL command. 5 PROFILE profile-name?Specifies a profile to be used on the network. The profile-name@is a character string of up to 32 characters. This parameter isAmandatory. Refer to the Public Network Information manual for thevalid profile-name.0 ! end of network parameters 4 Examples@ NCP>SET MODULE X25-PROTOCOL DTE 123789456 NETWORK TELENET -B _ CHANNELS 20-10,3,9 LINE DUP-0 MAXIMUM CIRCUITS 400 STATE ON?  This command creates a record for your local DTE (DTE B address 123789456) and associates a line DUP-0 and a set + of logical channels with this DTE.; NCP>SET MODULE X25-PROTOCOL NETWORK NET1 PROFILE PSDNCA This command specifies that you are going to use PSDNC, @ and that you are going to connect to this PSDN through  the network NET1.= NCP>SET MODULE X25-PROTOCOL GROUP ESECUG DTE 123789456 - _ NETWORK NET1 NUMBER 12= This command specifies that your DTE is a member of 7 closed user group ESECUG with group number 12.! 3 X25-SERVERCUse the SET MODULE X25-SERVER and SET MODULE X29-SERVER commands toCcreate or modify the parameters of the X.25 or X.29 Call Handler inCthe volatile data base. Use the DEFINE MODULE X25-SERVER and DEFINEDMODULE X29-SERVER commands to create or modify the parameters of the6X.25 or X.29 Call Handler in the permanent data base.   >Use separate SET/DEFINE MODULE X25-SERVER or SET/DEFINE MODULE<X29-SERVER commands to specify the module parameters and theCdestinations. The server modules contain records that identify andAspecify parameters for a destination, specify a maximum number ofEcircuits that each module (that is, all destinations for a particular8module) may have, and specify the state of the module. #SET MODULE X25-SERVER ALL /DEFINE X29-SERVER COUNTER TIMER seconds0 MAXIMUM CIRCUITS count& STATE ON % OFF' SHUT <SET MODULE X25-SERVER DESTINATION dest-name dest-params1DEFINE X29-SERVER KNOWN DESTINATIONS @All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 4 ALL >Copies the Call Handler parameters from the permanent database8into the volatile database.  Use only for the SET MODULE9X25-SERVER command or the SET MODULE X29-SERVER command. 4 COUNTER_TIMER_seconds <Sets a timer whose expiration causes a server module counter9logging event. Specify a decimal integer in the range 1 to 65,535. 4 DESTINATION_dest-name 7Identifies a destination. Dest-name is an id string. <SET MODULE X25-SERVER DESTINATION dest-name dest-paramsDEFINE X29-SERVER @The DESTINATION qualifier must be followed by one or more of the>following dest-params:  5 ACCOUNT account AIdentifies the user account used in connecting to a host node for>incoming calls to a destination. Specify a string of from 1 3to 39 characters. By default, no account is used. 5 ALL=Copies the destination parameters from the permanent database9into the volatile database. Use only with the SET MODULE0X25-SERVER or the SET MODULE X29-SERVER command.5 CALL_MASK hex-value ASpecifies the mask applied to the incoming call data before it isAtested. Hex-value is a string of 2 to 32 hexadecimal digits. Bydefault, no mask is used. 5 CALL_VALUE hex-value :Specifies the string used to test the incoming call data. AHex-value is a string of 2 to 32 hexadecimal digits. By default,no value is used. 5 CALLED ADDRESS dte-addrAFor redirected calls, this parameter identifies the DTE that was :originally called. The parameter value is used to select aAdestination for a redirected call. By default, no called DTE isused.5 EXTENSION_MASK hex-stringAProvides a mask for the called address extension facility. Using Alogical AND, the mask is merged with the called address extension9in the incoming call and the result is compared with the6extension value. By default no extension mask is used.5 EXTENSION_VALUE hex-string@Provides a value for the called address extension facility. This=value is compared with the address extension in the incoming@call (after merging as described in EXTENSION MASK). By defaultno extension value is used.5 GROUP group-name =Identifies a closed user group (CUG) or bilateral closed user>group (BCUG). The group-name is an id string. By default, nogroup name is used. 5 INCOMING ADDRESS dte-addr8Identifies the address of the DTE receiving the call (asspecified in the call packet).5 NETWORK net-name@Specifies the network for which calls are accepted. By default,no network n ame is used.5 5 NODE node-id?Identifies the P.S.I. Access node that is to be the destination9of the incoming X.25 call. Specify this parameter if theAexecutor node is a VMS node with VAX P.S.I. software in multihost?mode installed, serving as a connector node. This parameter is@mandatory when you specify this destination for first time. Use8only with the SET MODULE X25-SERVER or the DEFINE MODULEX25-SERVER command.5 OBJECT o bject-id ;Identifies the object used in connecting to a host node forAincoming calls to a destination. The object-id is an ID string. =If the object name looks like a number, enclose the string in@quotation marks. This parameter is mandatory when you specify a destination for the first time. 5 PASSWORD password <Specifies the password used in connecting to a host node for=incoming calls to a destination. Specify a string of from 1 <to 39 characters. The default is that no password is used.  5 PRIORITY priority ?Specifies the priority of the destination record and is used to?select one of a set of destinations for which the incoming call?may be valid. Specify a value in the range 0 to 255, where 255=is the highest priority. By default, priority takes a value of 0. 5 RECEIVING DTE dte-addr@Identifies the local DTE. It is used to select a destination for?calls received on the local DTE. By default, no receiving DTEis used.5 REDIRECT REASON code@Identifies a reason for redirecting an incoming call. The reason*code can take one of the following values:? BUSY The original DTE was busy and could not accept  any more calls.2 OUT OF ORDER The original DTE was out of order.@ SYSTEMATIC All calls to the original DTE are automatically  rerouted.BThe reason code is used to select a destination for a redirected $call. By default, no reason is used.5 SENDING ADDRESS dte-addr<Identifies the address of the remote DTE that originated the*call. By default, no sending DTE is used.5 SUBADDRESSES range ?Specifies the range of local DTE subaddresses that identify the?destination for the incoming call. Range consists of one or twoBsubaddresses. The subaddress is a decimal integer in the range 0 :to 9999. See the Public Network Information manual for the@maximum length of the subaddress for your network. Separate two;subaddresses with a single hyphen to indicate a range. TheAsecond subaddress must be greater than the first. By default, nosubaddress range is used. " 5 USER user-id >Specifies the user identification for use by incoming calls to?the destination. Specify a string of from 1 to 16 characters. ;The default is that no user identification is used.  4 KNOWN DESTINATIONS#Specifies all known destinations. 9SET MODULE X25-SERVER KNOWN DESTINATIONS dest-paramsDEFINE X29-SERVER =The KNOWN DESTINATIONS qualifier must be followed with one or!more of the following parameters: 5 ACCOUNT account AIdentifies the user account used in connecting to a host node for>incoming calls to a destination. Specify a string of from 1 3to 39 characters. By default, no account is used. 5 ALL=Copies the destination parameters from the permanent database9into the volatile database. Use only with the SET MODULE0X25-SERVER or the SET MODULE X29-SERVER command.. 5 CALL_MASK hex-value ASpecifies the mask applied to the incoming call data before it isAtested. Hex-value is a string of 2 to 32 hexadecimal digits. Bydefault, no mask is used. 5 CALL_VALUE hex-value :Specifies the string used to test the incoming call data. AHex-value is a string of 2 to 32 hexadecimal digits. By default,no value is used. 5 CALLED ADDRESS d te-addrAFor redirected calls, this parameter identifies the DTE that was :originally called. The parameter value is used to select aAdestination for a redirected call. By default, no called DTE is5used. 5 EXTENSION_MASK hex-stringAProvides a mask for the called address extension facility. Using Alogical AND, the mask is merged with the called address extension9in the incoming call and the result is compared with the6extension value. By default no extension mask is used.5 EXTENSION_VALUE hex-string@Provides a value for the called address extension facility. This=value is compared with the address extension in the incoming@call (after merging as described in EXTENSION MASK). By defaultno extension value is used.5 GROUP group-name =Identifies a closed user group (CUG) or bilateral closed user>group (BCUG). The group-name is an id string. By default, nogroup name is used. 5 INCOMING ADDRESS dte-addr8Identifies the address of the DTE receiving the call (asspecified in the call packet).5 NETWORK net-name@Specifies the network for which calls are accepted. By default,no network name is used.5 5 NODE node-id?Identifies the P.S.I. Access node that is to be the destination9of the incoming X.25 call. Specify this parameter if theAexecutor node is a VMS node with VAX P.S.I. software in multihost?mode installed, serv ing as a connector node. This parameter is@mandatory when you specify this destination for first time. Use8only with the SET MODULE X25-SERVER or the DEFINE MODULEX25-SERVER command.5 OBJECT object-id ;Identifies the object used in connecting to a host node forAincoming calls to a destination. The object-id is an ID string. =If the object name looks like a number, enclose the string in@quotation marks. This parameter is mandatory when you specify a destination for the first ti me. A5 PASSWORD password Specifies the password used in connecting to;a host node for incoming calls to a destination. Specify a:string of from 1 to 39 characters. The default is that no-password is used.  5 PRIORITY priority ?Specifies the priority of the destination record and is used to?select one of a set of destinations for which the incoming call?may be valid. Specify a value in the range 0 to 255, where 255=is the highest priority. By default, priority takes a value of 0. 5 RECEIVING DTE@Identifies the local DTE. It is used to select a destination for?calls received on the local DTE. By default, no receiving DTEis used.5 REDIRECT REASON code@Identifies a reason for redirecting an incoming call. The reason+code can take one of the following values:? BUSY The original DTE was busy and could not accept  any more calls.2 OUT OF ORDER The original DTE was out of order.@ SYSTEMATIC All calls to the original DTE are automatically  rerouted.AThe reason code is used to select a destination for a redirected $call. By default, no reason is used.5 SENDING ADDRESS dte-addr<Identifies the address of the remote DTE that originated the*call. By default, no sending DTE is used.5 SUBADDRESSES range ?Specifies the range of local DTE subaddresses that identify the?destination for the incoming call. Range consists of one or twoBsubaddresses. The subaddress is a decimal integer in the range 0 :to 9999. See the Public Network Information manual for the@maximum length of the subaddress for your network. Separate two;subaddresses with a single hyphen to indicate a range. TheAsecond subaddress must be greater than the first. By default, nosubaddress range is used. " 5 USER user-id >Specifies the user identification for use by incoming calls to?the destination. Specify a string of from 1 to 16 characters. CThe default is that no user identification is used. 4 MAXIMUM CIRCUITS count >Specifies the maximum number of circuits that the module (thatAis, all destinations) may have. By default, the maximum is 512. 4 STATE module-state;Specifies the operational state of the server module. This-parameter takes one of the following values: @ ON The module is available for normal use. For the X.252 server module, ON is the default state.B OFF The module is not in use. For the X.29 server module, $ OFF is the default state.E SHUT The module is to be closed down but only when all ? present activity has ceased. The SHUT value applies ; only to the SET MODULE X25-SERVER or X29-SERVER  command. 4 ExamplesC NCP>SET MODULE X25-SERVER DESTINATION JOE SUBADDRESSES 12-24 -9 _ SENDING ADDRESS 987321654 PRIORITY 3 OBJECT OBJONEA  This command creates a destination called JOE that will B handle incoming X.25 calls from a DTE with an address of : 987321654 and a subaddress in the range 12 to 24 1 specified in the DECnet object database.? NCP>SET MODULE X25-SERVER DESTINATION DEFDES OBJECT LAST - _ PRIORITY 0B This command modifies the destination called DEFDES that B will handle any incoming calls. The destination has the A lowest priority and will on ly handle calls that fail to " find another destination.3 NCP>SET MODULE X25-SERVER DESTINATION THRUSH -/ _ SUBADDRESSES 11-20 OBJECT 36 NODE THRUSHC This command creates a destination called THRUSH for node ; THRUSH that will match incoming X.25 calls with a A subaddress in the range 11 to 20. This command is used < if the executor node is a VMS node with VAX P.S.I. < software in multihost mode installed, serving as a A  connector node. Object 36 is the object number for VAX * P.S.I. Access on the remote node. 3 X29-SERVERCUse the SET MODULE X29-SERVER and SET MODULE X25-SERVER commands toCcreate or modify the parameters of the X.29 or X.25 Call Handler inCthe volatile data base. Use the DEFINE MODULE X29-SERVER and DEFINEDMODULE X25-SERVER commands to create or modify the parameters of the6X.29 or X.25 Call Handler in the permanent data base.  >Use separate  SET/DEFINE MODULE X29-SERVER or SET/DEFINE MODULE<X25-SERVER commands to specify the module parameters and theCdestinations. The server modules contain records that identify andAspecify parameters for a destination, specify a maximum number ofEcircuits that each module (that is, all destinations for a particular6module) may have, and specify the state of the module.* #SET MODULE X29-SERVER ALL /DEFINE X25-SERVER COUNTER TIMER seconds0 MAXIMUM CIRCUITS count& STATE ON % OFF' SHUT <SET MODULE X29-SERVER DESTINATION dest-name dest-params1DEFINE X25-SERVER KNOWN DESTINATIONS ?Please refer to help on SET MODULE X25-SERVER for more details.! 2 NODECUse the SET NODE command to create or modify node parameters in theEvolatile database on the local node. Use the DEFINE NODE command toGcreate or modify node parameters in the permanent database on the localnode.2 SET KNOWN NODES (parameters ...) DEFINE NODE node-id@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ALLFUse the SET NODE ALL command to update the volatile database on theFexecutor node with all the parameters stored for a particular node in,the permanent database on the executor node.3 ACCESSFSpecifies the allowed logical link connections for the node. There are four options:E INCOMING Allows logical link connections from the remote node.D OUTGOING Allows the local node to initiate connections to theD remote node, but does not allow connections from the remote node.F BOTH Allows incoming and outgoing logical link connections.$ This is the default.@ NONE Does not allow incoming or outgoing logical link) connections to this node.3 ADDRESS node-addressFSpecifies the address of the node to which you want the database entry to refer.3 CIRCUIT circuit-idFIdentifies a loop node and specifies the identification of the circuit,to be used for all traffic to the loop node.3 COUNTER TIMER seconds@Specifies a timer whose expiration causes a node counter logging:event. Seconds must be a decimal integer from 1 to 65,535.3 CPU cpu-type<Identifies the node's CPU type. There are four valid types: DECSYSTEM1020 PDP11 PDP8 VAX3 DIAGNOSTIC FILE file-specBApplies to nodes on broadcast circuits. Identifies the file to be=read when the adjacent node has been downline loaded and has Drequested diagnostics. The file-spec is interpreted according to the!file system of the executor node. 3 DUMP_ADDRESS number?Identifies the address in memory to begin an upline dump of theadjacent node. 3 DUMP_COUNT numberDSpecifies the default number of memory units to upline dump from thethe adjacent node. 3 DUMP_FILE file-specBIdentifies which file to write to when the adjacent node is dumpedupline. 3 HARDWARE ADDRESS h-addressBIdentifies the address originally assigned to the controller for Athe system on the adjacent node. Used during operations such as Fdownline loading to communicate with the system before the system has set up its physical address.3 HOST node-idFIdentifies the hos t node. For an adjacent node, the host address is aEparameter that the adjacent node receives when it is loaded downline.:If no host is specified, the default is the executor node.3 INBOUND node-type=Required for nodes when the VERIFICATION INBOUND parameter isBspecified for the DDCMP circuit over which the connection is to beFmade. Specifies the type of the node. The node-type is checked by the>executor node if the specified node attempts to form a dynamicBconnection with the executor node. If VERIFICATION INBOUND is not@specified for the circuit, the INBOUND parameter for the node is1ignored. The two possible node-types are:  @ENDNODE Allows the remote node to be connected only if it is % configured as an end node.@ROUTER Allows the remote node to be connected whether it is 1 configured as an end node or a router. 3 KNOWN NODESEIndicates that the specified parameters for all known nodes are to be$created or modified in the database.3 LOAD_ASSIST_AGENT file-spec@Specifies the VMS image that will define the system software forFdownline loading and adjacent node. The load assist agent can be usedBto tailor the system software to be loaded. The LOAD ASSIST AGENT;parameter applies to downline load operations to Local AreaVAXclusters only. 3 LOAD_ASSIST_PARAMETER itemDSpecifies a parameter to be passed to a load assist agent. The LOADCASSIST PARAMETER value applies to downline load operations to LocalArea VAXclusters only. 3 LOAD_FILE file-specDSpecifies a file containing the system software for downline loadingto an adjacent node.3 MANAGEMENT FILE file-spec?Specifies a file containing management information for downlineloading to an adjacent node.3 NAME node-name7Specifies the node name to be associated with the node Didentification. Only one name can be assigned to a node address or a line identification.3 NODE node-idDIdentifies the node (local or remote) for which specified parameters.are to be created or modified in the database.3 NONPRIVILEGED itemBSpecifies nonprivileged inbound access control information for theGnode. Associate any of the following parameters with the NONPRIVILEGED parameter: @ ACCOUNT account Identifies the account for the default F nonprivileged DECnet account on the designated  node.A PASSWORD password Identifies the password for the default F nonprivileged DECnet account on the designated node.B USER user-id Identifies the user name for the default F nonprivileged DECnet account on the designated node.3 PRIVILEGED itemFSpecifies privileged inbound access control information for the node.HAssociate any of the following paramet ers with the PRIVILEGED parameter: @ ACCOUNT account Identifies the account for the default C privileged DECnet account on the designated node.A PASSWORD password Identifies the password for the default C privileged DECnet account on the designated node.B USER user-id Identifies the user name for the default C privileged DECnet account on the designated node.3 RECEIVE PASSWORD hex-passwordFDefines the password (1-8 characters) that is expected from the remoteBnode during a Routing initialization sequence. Use this parameterBonly if verification is enabled or set to INBOUND for the circuit. 3 SECONDARY LOADER file-specBSpecifies a file containing the secondary boot loader for downlineloading to an adjacent node.3 SERVICE_CIRCUIT circuit-idDEstablishes the circuit to be used for downline loading. This is theGdefault value for the VIA parameter of the LOAD and CONNECT commands. 8The node identification must be that of the target node.3 SERVICE_DEVICE device-typeDIdentifies the target node's line controller for the service circuit@over which the operation is to take place. See HELP PARAMETERS 3DEVICE-TYPE for a list of circuit and line devices.BOnly the synchronous port on the DMF service device may be used. 3 SERVICE_NODE_VERSION version CSpecifies the DECnet for OpenVMS software version of the node which@downline loads its software to a target node. The two possible>versions are PHASE III and PHASE IV. The default is PHASE IV.! 3 SERVICE_PASSWORD hex-passwordDIdentifies the password required to trigger the bootstrap mechanismAon the target node. The password is a hexadecimal number. ForADDCMP circuits, the password is in the range 0 to FFFFFFFF; forFbroadcast circuits, it is in the range 0 to FFFFFFFFFFFFFFFF. The default is 0.%3 SOFTWARE_IDENTIFICATION software-idBIs the ID of the software to be downline loaded. You include this;parameter only if the SOFTWARE TYPE parameter is specified. 3 SOFTWARE_TYPE software-type?Identifies a particular file type to be loaded. There are fourpossibilities: MANAGEMENT FILE SECONDARY LOADER TERTIARY LOADER SYSTEM3 TERTIARY LOADER file-spec?Specifies a file containing a tertiary boot loader for downlineloading to an adjacent node. 3 TRANSMIT PASSWORD passwordDSpecifies a password (1-8 characters) sent to the remote node during@a Routing initialization sequence. Does not apply to nodes on aCbroadcast circuit. This parameter is used only if the VERIFICATION=parameter has been set to ENABLED or INBOUND for the circuit. 3 Examples! NCP>SET NODE 5.14 NAME DENVER? This command sets the node name of node 5.14 t o DENVER. F NCP>SET NODE 2.11 NONPRIVILEGED USER NETNONPRIV PASSWORD NONPRIV -+ _ PRIVILEGED USER NETPRIV PASSWORD PRIVE This command establishes default privileged and nonprivileged1 access control information for node 2.11. NCP>SET NODE 14 ADDRESS 2D This command associates the information for node 1.14 with aE new node whose address is 1.2. This example assumes that theF executor is in area 1 and that the network is not divided into multiple areas.8 NCP>SET NODE LARK HARDWARE ADDRESS 08-00-2B-34-55-FF@ This command associates with the node LARK the hardware ? address originally assigned to the DESVA controller at A node LARK. This information in the volatile database canC be used during downline loading of target node LARK over an Ethernet circuit. NCP>SET KNOWN NODES ALLA This command loads all permanent database entries stored 7 for all known nodes into the volatile database.% NCP>SET NODE TESTER CIRCUIT FZA-0D This command sets the loop node name (TESTER) and identifiesE the circuit over which loop information is to be transmitted.! 2 OBJECTGUse the SET OBJECT command to create or modify object parameters in theFvolatile database on the local node. Use the DEFINE OBJECT command toCcreate or modify object parameters in the permanent database on the local node.2 SET OBJECT object-name (parameters ...) DEFINE KNOWN OBJECTS@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ACCOUNT accountCIdentifies the default user's account for access control on inboundAconnects to the object when no access control is specified by theremote node. & FFor VAX PSI, identifies theuser account for use by incoming X.25 calls4to the object; if not specified, no account is used. 3 ALIAS_INCOMING option@Does not apply to VAX P.S.I. Specifies how a particular object Aresponds to incoming connect requests directed to the alias node >address. The alias node address is established using the SETGEXECUTOR command. There are two options for ALIAS INCOMING: C ENABLED Allows a specified object to receive incoming connect@ requests that have been directed to the alias nodeD address. An ob ject such as PHONE which uses a protocolC that depends on multiple links should not be enabled? for ALIAS INCOMING. By default, if an alias node> identifier has been specified, ALIAS INCOMING is7 enabled for all objects except for PHONE.C DISABLED Does not allow a specified object to receive incomingC connect requests that have been directed to the alias> node address. An object whose resources are notD  accessible cluster wide should not have ALIAS INCOMING? disabled. If an attempt is made to connect to anC object that does not have ALIAS INCOMING enabled, the8 status message NO SUCH OBJECT is returned.3 ALIAS_OUTGOING optionDSpecifies whether a particular object uses the alias node identifier>specified in the SET EXECUTOR command in its outgoing connect Brequests and other protocols. Specify either of the following twooptions: BENABLED Allows a specified object to use the alias node address E in its outgoing connect requests. An object such as PHONE G which uses a protocol that depends on multiple links should F not have the ALIAS OUTGOING parameter enabled. By default, : only the object MAIL has ALIAS OUTGOING enabled.ADISABLED Does not allow a specified object to use the alias node3 address in its outgoing connect requests.3 ALLEThe SET object-component ALL command to updates the volatile databaseFwith all the object parameters stored in the permanent database for a'particular object or all known objects. 3 FILE file-specCSpecifies the command file containing the command procedure used to@start the indicated object. If not specified, the default is: SYS$SYSTEM:object-name.COM@When you specify an object for the first time, this parameter is mandatory. 3 KNOWN OBJECTSCIndicates that the specified parameters are applicable to all knownobjects.3 NUMBER numberBSpecifies the object number. Numbers 1 through 127 are for use byEDigital Equipment Corporation. Numbers 0 and 128 through 255 are forFcustomer use. See the DECnet for OpenVMS Network Management UtilitiesEmanual for a comprehensive list of reserved object numbers. When youDspecify an object for the first time, this parameter is mandatory. 3 OBJECT object-nameFIdentifies the object for which specified parameters are to be createdor modified in the database. ,3 OUTGOING CONNECT PRIVILEGES privilege-listBSpecifies the privileges that a user must possess in order to make%outbound connections to the object. 3 PASSWORD passwordDIdentifies the default user's password for access control on inboundAconnects to the object when no access control is specified by theCremote node. This password must match the password established forthe account. 3 PRIVILEGES privilege-list DSp ecifies those privileges normally required by the object. A user Gwith those privileges may be supplied with default outbound privileged :access control information when connecting to the object.  3 PROXY option FAssigns the proxy login access defaults to individual objects. Specify"one of the following four options:1 INCOMING Allows proxy login to the object.A OUTGOING Allows logical links using the object to request / proxy login on the remote node.E BOTH Allows both incoming and outgoing proxy login access.+ This is the default option.? NONE Does not allow incoming or outgoing proxy login access.3 USER user-idBIdentifies the default user's identification for access control onEinbound connects to the object when no access control is specified bythe remote node. 3 Examples) NCP>SET OBJECT NML FILE NML NUMBER 19< This command sets an object number, 19, for the NML  object.1 NCP>SET OBJECT NML PRIVILEGES OPER DIAGNOSE - _ USER NET_NONPRIV - _ PASSWORD NET_NONPRIV9 This command establishes default access control 7 information for the NML object and sets those 7 privileges required to connect to this object.= NCP>SET OBJECT OBJONE FILE OBJONE.COM NUMBER 0 USER NET - _ PASSWORD NET< This command creates an object called OBJONE with a ; command procedure called OBJONE.COM. The incoming > connection uses a password and user identification of NET.$ NCP>SET EXECUTOR ALIAS NODE 2.13- NCP>SET OBJECT FOX ALIAS OUTGOING ENABLED8 The SET EXECUTOR ALIAS NODE command establishes : address 2.13 as the alias node identifier for the ; local node. The SET OBJECT command associates the : object FOX with the alias node identifier for all " outgoing connect requests. NCP>SET OBJECT T* PROXY NONE9 This command prevents incoming or outgoing proxy ? login access for all objects with names beginning with "T".@ NCP>SET OBJECT TEST OUTGOING CONNECT PRIVILEGES READALL OPER= This command specifies that a user process must have A privileges READALL and OPER in order to make an outbound " connection to object TEST.! ww ,1 SHOWFUse the SHOW command to display information from the volatile databaseBon the executor node. Use the LIST command to display information1from the permanent database on the executor node.@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. ! 2 AREA?Use the SHOW AREA command to display area information from the 5volatile database available to the local node or DTE.;SHOW ACTIVE AREAS CHARACTERISTICS TO file-id# AREA area-id SUMMARY" KNOWN AREAS STATUS@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ACTIVE AREAS CIndicates that information for all active areas is to be displayed.3 AREA area-idFIdentifies a particular area for which information is to be displayed. displayed.3 CHARACTERISTICS5Indicates that static information is to be displayed. 3 KNOWN AREASBIndicates that information for all known areas is to be displayed.3 STATUS6Indicates that dynamic information is to be displayed. 3 SUMMARY8Indicates that only the most useful information is to bedisplayed. This is the default. 3 TO file-id;Specifies the output file. If none is specified, SYS$OUTPUTis the default. 3 Examples NCP>SHOW KNOWN AREAS STATUSE This example displays status information for all known areas in the network. NCP>SHOW AREA 11 SUMMARY D This example displays only the most useful information for area 11 in the network.! 2 CIRCUITEUse the SHOW CIRCUIT command to display circuit information (from the3volatile database) available to the executor node. DSHOW ACTIVE CIRCUITS CHARACTERISTICS ADJACENT NODE node-id9 KNOWN CIRCUITS COUNTERS TO file-id" CIRCUIT circuit-id STATUS# SUMMARYFUse the LIST CIRCUIT command to display circuit information (from the 4permanent database) available to the executor node.DLIST KNOWN CIRCUITS CHARACTERISTICS ADJACENT NODE node-id9 CIRCUIT circuit-id COUNTERS TO file-id" STATUS# SUMMARY@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ACTIVE CIRCUITS;Indicates that information for all active circuits is to be3displayed. Use only with the SHOW CIRCUIT command.3 ADJACENT NODE node-id9Indicates that the display of a list of circuits is to be5restricted to those circuits leading to the specifiedadjacent node.3 CHARACTERISTICS5Indicates that static information is to be displayed.3 CIRCUIT circuit-id>Identifies a particular circuit for which information is to be displayed. 3 COUNTERS9Indicates that error and performance statistics are to be=displayed. Valid for circuits, lines, the executor and nodes.3 KNOWN CIRCUITS:Indicates that information for all known circuits is to be displayed.3 STATUS6Indicates that dynamic information is to be displayed. 3 SUMMARY8Indicates that only the most useful information is to bedisplayed. This is the default. 3 TO file-id;Specifies the output file. If none is specified, SYS$OUTPUTis the default. 3 Examples$ NCP>SHOW CIRCUIT DMC-0 COUNTERS? This command displays circuit counter information for 0 circuit DMC-0 on the SYS$OUTPUT device. NCP>SHOW ACTIVE CIRCUITS@ This command displays circuit summary information for 0 all circuits that are in the ON state.1 NCP>SHOW KNOWN CIRCUITS ADJACENT NODE BOSTONC This command displays summary information for all circuits+ connected to adjacent node BOSTON.! 2 EXECUTORHUse the SHOW EXECUTOR command to display executor node information (fromIthe volatile database). Use the LIST EXECUTOR command to display executorBnode information (from the permanent database). /  :SHOW EXECUTOR CHARACTERISTICS TO file-id LIST COUNTERS STATUS SUMMARY3 CHARACTERISTICS5Indicates that static information is to be displayed. 3 COUNTERS9Indicates that error and performance statistics are to be=displayed. Valid for circuits, lines, the executor and nodes.3 STATUS6Indicates that dynamic information is to be displayed. 3 SUMMARY8Indicates that only the most useful information is to bedisplayed. This is the default. 3 TO file-id;Specifies the output file. If none is specified, SYS$OUTPUTis the default. 3 Examples& NCP>SHOW EXECUTOR CHARACTERISTICSE This command displays characteristics for the executor node " on the SYS$OUTPUT device. NCP>SHOW EXECUTORC This command displays executor node summary information.  This is the default.* NCP>SHOW EXECUTOR COUNTERS TO NET.LOG= This command writes executor and local node counter % information to file NET.LOG. NCP>SHOW EXECUTOR COUNTERS1 Node Counters as of 6-AUG-1992 13:34:53' Executor node = 4.710 (LNDLEE)- 307 Seconds since last zeroed" 0 Bytes received 0 Bytes sent% 0 Messages received! 0 Messages sent% 0 Connects received!  0 Connects sent% 0 Response timeouts4 0 Received connect resource errorsG 2 Maximum logical links active <- Executor countersA 0 Aged packet loss start here.0 0 Node unreachable packet loss1 0 Node out-of-range packet loss) 0 Oversized packet loss' 0 Packet format error/ 0 Partial routing update loss'  0 Verification rejectD This command displays the counter information for both the E local node and the executor. The counters for the executor E node are always displayed. The counters for the local node @ are displayed only after the first link is established + between the executor and itself. ! 2 LINE<Use the SHOW LINE command to display line information (from 8the volatile database) available to the executor node. 7SHOW ACTIVE LINES CHARACTERISTICS TO file-id KNOWN LINES COUNTERS LINE line-id STATUS SUMMARY<Use the LIST LINE command to display line information (from 7the permanent database) available to the executor node.7LIST KNOWN LINES CHARACTERISTICS TO file-id LINE line-id COUNTERS STATUS SUMMARY3 ACTIVE LINES8Indicates that information for all active lines is to be:displayed. Only use this parameter with the SHOW command.3 CHARACTERISTICS5Indicates that static information is to be displayed. 3 COUNTERS9Indicates that error and performance statistics are to be=displayed. Valid for circuits, lines, the executor and nodes. 3 KNOWN LINES7Indicates that information for all known lines is to be displayed.3 LINE line-id;Identifies a particular line for which information is to be displayed.3 STATUS6Indicates that dynamic information is to be displayed. 3 SUMMARY8Indicates that only the most useful information is to be displayed. This is the default. 3 TO file-id<Specifies the output file. If none is specified, SYS$OUTPUTis the default. 3 Examples! NCP>SHOW LINE DMC-0 COUNTERS< This command displays line counter information for - line DMC-0 on the SYS$OUTPUT device. NCP>SHOW ACTIVE LINES< This command displays line summary information for , all lines that are in the ON state.! 2 LINKS@Use the SHOW LINKS command to display link information (from the2volatile database) available to the executor node.ASHOW KNOWN LINKS CHARACTERISTICS TO file-id, KNOWN LINKS WITH NODE node-id STATUS- LINK number SUMMARY@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 CHARACTERISTICS5Indicates that static information is to be displayed. 3 KNOWN_LINKS7Indicates that information for all known links is to be displayed.3 KNOWN_LINKS_WITH_NODE node-id:Indicates that information for all links to the designatednode is to be displayed. 3 LINK number+Displays information about a specific link.3 STATUS6Indicates that dynamic information is to be displayed. 3 SUMMARY8Indicates that only the most useful information is to be displayed. This is the default. 3 TO file-id<Specifies the output file. If none is specified, SYS$OUTPUTis the default. 3 Examples NCP>SHOW KNOWN LINKS< This command displays link summary information for / all links active on the executor node.4 NCP>SHOW KNOWN LINKS WITH NODE TRNTO TO NET.LOG: This command writes link summary information for 8 all active links with remote node TRNTO to the  file NET.LOG.! 2 LOGGINGEUse the SHOW LOGGING command to display logging information (from the4 volatile database) available to the executor node. ESHOW ACTIVE LOGGING CHARACTERISTICS SINK NODE node-id TO file-id3 KNOWN LOGGING EVENTS KNOWN SINKS' LOGGING CONSOLE STATUS  LOGGING FILE SUMMARY LOGGING MONITOREUse the LIST LOGGING command to display logging information (from the4permanent database) available to the executor node. ELIST KNOWN LOGGING CHARACTERISTICS SINK NODE node-id TO file-id3 LOGGING MONITOR SUMMARY KNOWN SINKS' LOGGING CONSOLE STATUS ' LOGGING FILE EVENTS @All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ACTIVE LOGGING:Indicates that information for all active logging is to be displayed. 3 CONSOLE;Indicates that information for the logging console is to be displayed.3 FILE8Indicates that information for the logging file is to be displayed.3 KNOWN_LOGGING9Indicates that information for all known logging is to be displayed. 3 KNOWN_SINKS7Indicates that information for all known sinks is to be2displayed. If unspecified, only the executor node is displayed. 3 MONITOR;Indicates that information for the logging monitor is to be displayed.3 SINK NODE node-id:Identifies a particular sink node for which information isto be displayed.3 CHARACTERISTICS5Indicates that static information is to be displayed.3 EVENTS9Indicates that logging event filters are to be displayed.3 STATUS6Indicates that dynamic information is to be displayed. 3 SUMMARY8Indicates that only the most useful information is to be displayed. This is the default. 3 TO file-id<Specifies the output file. If none is specified, SYS$OUTPUTis the default. 3 Examples' NCP>SHOW KNOWN LOGGING KNOWN SINKS; This command displays logging summary information 2 for all known logging at all known sinks.1 NCP>SHOW LOGGING FILE EVENTS SINK NODE TRNTO9 This command displays events that are currently 8 being logged to the logging file at node TRNTO.! 2 MODULEIntroduce the MODULE entities.3 CONFIGURATOR@The SHOW MODULE CONFIGURATOR command shows information about theDEthernet configurator module from the volatile database at the local:node. Use the LIST MODULE CONFIGURATOR command to display7the information stored in the permanent database. Note,the word MODULE is  optional.7 FSHOW MOD CONFIGURATOR KNOWN CIRCUITS CHARACTERISTICS TO file-id1LIST CIRCUIT circuit-id STATUS2 SUMMARY@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 4 CHARACTERISTICS@Indicates that dynamic information on all active systems on the <specified Ethernet circuit or circuits is to be displayed. 8(Characteristics and Status result in a similar display)4 CIRCUIT circuit-id@Applies only to Ethernet circuits. Indicates that configurator >information should be displayed only for the Ethernet circuit identified by circuit-id.4 KNOWN CIRCUITS?Applies only to Ethernet circuits. Indicates the configurator @information should be displayed for all known Ethernet circuits.4 STATUS@Indicates that dynamic information on all active systems on the <specified Ethernet circuit or circuits is to be displayed. 8(Characteristics and Status result in a similar display) 4 SUMMARYCIndicates that the only information to be displayed is the list of Acircuits being monitored and the length of time surveillance has +been maintained. This is the default type.4 TODSpecifies the output file. If none is specified, SYS$OUTPUT is the default. 4 Examples> NCP>SHOW CONFIGURATOR KNOWN CIRCUITS SUMMARY TO PRINTFILEC This command causes summary information about surveillanceB on all known Ethernet circuits to be directed to the file PRINTFILE.7 NCP>SHOW MODULE CONFIGURATOR KNOWN CIRCUITS STATUSB This command displays information about active systems on: all Ethernet circuits known to the executor node. 3 X25-ACCESS CUse the SHOW MODULE X25-ACCESS command to display the parameters ofCthe Access Module from the volatile data base. Use the LIST MODULEAX25-ACCESS command to display the Access Module parameters storedin the permanent data base. CSHOW MOD X25-ACCESS NETWORK net-name CHARACTERISTICS TO file-id.LIST KNOWN NETWORKS STATUS/ SUMMARY4 CHARACTERISTICS!Displays static line information.4 NETWORK net-name5Displays information for the specified network only. 4 KNOWN NETWORKS-Displays information for all known networks. 4 STATUS%Displays dynamic module information. 4 SUMMARY>Displays only the most useful module information. This is thedefault display type. 4 TO file-idBSpecifies the output file. If you omit this parameter, the defaultfile is SYS$OUTPUT. 4 Examples7 NCP>SHOW MODULE X25-ACCESS KNOWN NETWORKS STATUS - _ TO MYFILE.NET8 This command writes status information for all : known X.25 networks to the file named MYFILE.NET.4 NCP>SHOW MODULE X25-ACCESS NETWORK PSS1 SUMMARY: This command displays static network info rmation + about the X.25 network named PSS1.3 X25-PROTOCOLEUse the SHOW MODULE X25-PROTOCOL command to display the parameters ofFthe Protocol Module from the volatile data base. Use the LIST MODULEEX25-PROTOCOL command to display the Protocol Module parameters stored9in the permanent data base. The word MODULE is optional.>SHOW X25-PROTOCOL GROUP group-name CHARACTERISTICS TO file+LIST KNOWN GROUPS COUNT, STAT US- SUMMARY>SHOW X25-PROTOCOL NETWORK net-name CHARACTERISTICS TO file+LIST KNOWN NETWORKS COUNT, STATUS- SUMMARYCSHOW X25-PROTOCOL DTE dte-addr NETWORK net-name CHAR TO file:LIST KNOWN DTES KNOWN NETWORKS COUNT; STATUS< SUMMARY@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 4 DTE dte-addr1Displays information for the specified DTE only. 4 GROUP group-name3Displays information for the specified group only. 4 KNOWN_DTES)Displays information for all known DTEs. 4 KNOWN_GROUPS+Displays information for all known groups. 4 KNOWN_NETWORKS-Displays information for all known networks. 4 NETWORK net-name5Displays information for the specified network only. 4 CHARACTERISTICS!Displays static line information. 4 COUNTERSCDisplays DTE error and performance statistics. (Used only with the#SHOW MODULE X25-PROTOCOL command.) 4 STATUS>Displays dynamic module information. (Used only with the SHOWMODULE X25-PROTOCOL command.) 4 SUMMARY>Displays only the most useful module information. This is thedefault display type. 4 TO file-idCSpecifies the output file. If you omit this parameter, the defaultfile is SYS$OUTPUT. 4 Examples > NCP>SHOW MODULE X25-PROTOCOL NETWORK FRED CHARACTERISTICS= This command displays module characteristics for the X25-PROTOCOL module.< NCP>SHOW MODULE X25-PROTOCOL KNOWN DTES CHARACTERISTICSA This command displays characteristics for all DTEs known$ to the X25-PROTOCOL module.1 NCP>SHOW MODULE X25-PROTOCOL DTE 123456789 -% _ NETWORK PSS-COMBINATION STATUSB This command displays the status of DTE 123456789 in the ! network PSS-COMBINATION.> NCP>SHOW MODULE X25-PROTOCOL DTE 123456789 NETWORK FRED - _ COUNTERS C This command displays information about each DTE counter. ! 3 X25-SERVEREUse the SHOW MODULE X25-SERVER and SHOW MODULE X29-SERVER commands toBdisplay the parameters of the X25 and X.29 Call Handlers stored in@the volatile data base. Use the LIST MODULE X25-SERVER and LISTFMODULE X29-SERVER commands to display the parameters of the X.25 andAX.29 Call Handlers stored in the permanent data base. Note thatkeyword MODULE is optional.ESHOW MOD X25-SERVER DESTINATION name CHARACTERISTICS TO File-id2LIST X29-SERVER KNOWN DESTINATIONS COUNTERS0 STATUS1 SUMMARY1SHOW MOD X25-SERVER CHARACTERISTICS TO File-idLIST X29-SERVER COUNTERS STATUS SUMMARY@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 4 CHARACTERISTICS!Displays static line information. 4 COUNTERSEDisplays module error and performance statistics. (Used only with the;SHOW MODULE X25-SERVER or SHOW MODULE X29-SERVER command.) 4 DESTINATION name9Displays information for the specified destination only. 4 KNOWN DESTINATIONS1Displays information for all known destinations. 4 STATUSDDisplays dynamic module information. (Used only with the SHOW MODULE/X25-SERVER or SHOW MODULE X29-SERVER command.) 4 SUMMARY>Displays only the most useful module information. This is thedefault display type. 4 TO file-idBSpecifies the output file. If you omit this parameter, the defaultfile is SYS$OUTPUT. 4 Examples/ NCP>SHOW MODULE X25-SERVER CHARACTERISTICSA This command displays characteristics for the X25-SERVER module.? NCP>LIST MODULE X25-SERVER DESTINATION XTR CHARACTERISTICSE This command displays server module characteristics from the0 permanent database for destination XTR.& NCP>SHOW MODULE X25-SERVER STATUSD This command displays status information for the X25-SERVER module.( NCP>SHOW MODULE X25-SERVER COUNTERSC This command displays counter information for each server  module.! 2 NODE?Use the SHOW NODE command to display node information (from theEvolatile database) available to the executor node. Use the LIST NODEAcommand to display node information (from the permanent database)available to the executor node.4SHOW LOOP NODES CHARACTERISTICS TO file-id LIST NODE node-id COUNTERS STATUS SUMMARY=In the following commands, the CIRCUIT parameter is optional.DSHOW ACTIVE NODES CIRCUIT circuit-id CHARACTERISTICS TO file-id1 ADJACENT NODES COUNTERS/ STATUS0 SUMMARYBSHOW KNOWN NODES CIRCUIT circuit-id CHARACTERISTICS TO file-id/LIST COUNTERS- STATUS. SUMMARY@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 ACTIVE NODESFFor a Routing node, indicates that information for all r eachable nodesEis to be displayed. For a nonrouting node (end node), indicates thatCinformation about the executor is to be displayed. Optionally, youDcan also specify a particular CIRCUIT parameter. Use this only withSHOW.A 3 ADJACENT NODES DIndicates that information for alladjacent node id to be displayed. BAdjacent nodes are those the executor perceives Routing can reach@that are separated from the executor by a  single circuit. EachAoccurrence of a node on a different circuit appears as a separateEadjacent node. Optionally, you can also specify a particular CIRCUIT$parameter. Use this only with SHOW. 3 CIRCUIT circuit-idESpecifies that the display of a list of nodes is to be restricted to .those nodes adjacent to the specified circuit. 3 KNOWN NODESCIndicates that information for all known nodes is to be displayed. <Optionally, you can specify a particular CIRCUIT parameter. 3 LOOP NODESAIndicates that information for all loop nodes is to be displayed.3 NODE node-id;Identifies a particular node for which information is to be displayed.3 CHARACTERISTICS5Indicates that static information is to be displayed. 3 COUNTERS9Indicates that error and performance statistics are to be displayed. 3 STATUS6Indicates that dynamic information is to be displayed. 3 SUMMARY8Indicates that only the most useful information is to bedisplayed. This is the default. 3 TO file-id;Specifies the output file. If none is specified, SYS$OUTPUTis the default. 3 Examples! NCP>SHOW KNOWN NODES SUMMARY8 This command displays node summary information  for all known nodes.$ NCP>SET NODE TEST CIRCUIT DMC-0 NCP>SHOW LOOP NODES8 The first command establishes a loop node name 7 (TEST) for the associated circuit DMC-0. The 2 second command displays loop node status 7 information for all loop nodes established by  the SET NODE command.! 2 OBJECTCUse the SHOW OBJECT command to display object information (from the@volatile database) available to the executor node. Use the LISTAOBJECT command to display object information (from the permanent *database) available to the executor node. :SHOW KNOWN OBJECTS CHARACTERISTICS TO file-id#LIST OBJECT object-name STATUS$ SUMMARY@All underscores found in parameters must be replaced with spaces)when parameters are used in NCP commands. 3 CHARACTERISTICS5Indicates that static information is to be displayed.3 KNOWN OBJECTS9Indicates that information for all known objects is to be displayed.3 OBJECT object-name:Identifies a particular object for which information is to be displayed.3 STATUS6Indicates that dynamic information is to be displayed. 3 SUMMARY8Indicates that only the most useful information is to bedisplayed. This is the default. 3 TO file-id;Specifies the output file. If none is specified, SYS$OUTPUTis the default. 3 Examples# NCP>SHOW KNOWN OBJECTS SUMMARY7 This command displays summary information for  all known objects.! ww@ ,1 TELLFUse the TELL prefix to identify the executor node for a particular NCPFcommand. TELL sets the executor for only one command and must prefix?the command for which it is intended.  This command allows youDoptionally to specify access control information in one of two ways:3as part of the node-spec or as distinct parameters.%TELL node-spec ACCOUNT account' PASSWORD password" USER user-idAYou cannot use the TELL prefix with the CLEAR EXECUTOR NODE, COPY+KNOWN NODES, or SET EXECUTOR NODE commands. 2 node-spec>Specifies a node name or address optionally followed by access@control information as specified for O penVMS systems. Use one ofthe following formats: node-id& node-id"user password account";The node-id can be a logical name. You can override access?control in a logical name by specifying explicit access controlinformation in the command. 2 ACCOUNT account@Identifies the user's account for access control verification atAthe designated executor node. This parameter is not required for>DECnet for OpenVMS nodes since DECnet for OpenVMS does not use=account info rmation to validate access control.  2 PASSWORD passwordAIdentifies the user's password for access control verification atthe designated executor node.. 2 USER user-id?Identifies the user's ID for access control verification at thedesignated executor node.- 2 Examples% NCP>TELL 3.5 SET KNOWN LINES ALL: This command sets the executor to node 3.5 where 2  the SET KNOWN LINES ALL command executes.. NCP>TELL TRNTO"LOW JBL" SHOW KNOWN LINES: This command uses access control information to 7 set the executor to node TRNTO where the SHOW & KNOWN LINES command executes.3 NCP>TELL TRNTO USER SYSTEM PASSWORD MANAGER -  _ ZERO EXECUTOR7 This command uses an alternate access control 8 format to set the executor to node TRNTO where , the ZERO EXECUTOR command executes.!  ww@ , 1 TRIGGER@Use the TRIGGER commands to trigger the bootstrap mechanism of aEtarget node such that the node will load itself. Use this command to7initiate the loading sequence for an unattended system.2 NODEDUse the TRIGGER NODE command to trigger the bootstrap mechanism of aEtarget node such that the node will load itself. Use this command to7initiate the loading sequence for an unattended system.8TRIGGER NODE node-id SERVICE PASSWORD hex-password  & VIA circuit-id2 PHYSICAL ADDRESS p-address 3 NODE node-id7Identifies the node whose bootstrap is to be triggered.3 PHYSICAL ADDRESS p-addressDApplies only to nodes on broadcast circuits. Specifies the physicalDaddress that the target node currently use to identify itself. TheDvalue is the physical address the target node has set for itself or,?if the target node has not set a physical address, the hardware<address associated wit h the target node's device controller.3 3 SERVICE PASSWORD hex-passwordFIdentifies the password required to trigger the bootstrap mechanism onEthe target node. The password is a hexadecimal number 8 to 16 digits6long. For broadcast circuits, it is in the range 0 to=FFFFFFFFFFFFFFFF. For DDCMP circuits, it is in the range 0 to FFFFFFFF.% 3 VIA circuit-idAIdentifies the circuit over which the operation is to take place. 3 Examples NCP>TRIGGER NODE NYC: This command triggers the bootstrap mechanism on 8 node NYC to initiate a downline load operation.9 NCP>TRIGGER NODE NYC SERVICE PASSWORD F0F0 VIA DMC-5; This command provides a service password in order 8 to trigger the bootstrap mechanism on node NYC 5 and initiate a downline load operation over  circuit DMC-5.! 2 VIACUse the TRIGGER VIA command to  trigger the bootstrap mechanism of aJtarget node using the specified circuit to allow the node to load itself. DUse this command to initiate the loading sequence for an unattended system. $ 8TRIGGER VIA circuit-id SERVICE PASSWORD hex-password5 PHYSICAL ADDRESS p-address3 SERVICE PASSWORD hex-passwordFIdentifies the password required to trigger the bootstrap mechanism onEthe target node. The password is a hexadeci mal number 8 to 16 digits6long. For broadcast circuits, it is in the range 0 to=FFFFFFFFFFFFFFFF. For DDCMP circuits, it is in the range 0 to FFFFFFFF.3 PHYSICAL ADDRESS p-addressDApplies only to nodes on broadcast circuits. Specifies the physicalDaddress that the target node currently uses to identify itself. TheEvalue is the physical address the target node has set for itself or,?if the target node has not set a physical address, the hardwareAaddress associated with the target node's device controller. ThisEparameter must be included if a broadcast circuit is specified in VIA circuit-id.> 3 VIA circuit-idAIdentifies the circuit over which the operation is to take place. 3 Examples NCP>TRIGGER VIA DMC-5B This command triggers the bootstrap mechanism on the node$ connected to circuit DMC-5.= NCP>TRIGGER VIA MNA-0 PHYSICAL ADDRESS AA-00-04-00-07-04> This command triggers the bootstrap mechanism on the A target node whose physical address is AA-00-04-00-07-04  on circuit MNA-0.! wwW)B ,1 ZEROFUse the ZERO commands to reset counters for circuits, lines, nodes and the executor. 2 EXECUTOR;Use the ZERO EXECUTOR command to reset all counters for the local node. ZERO EXECUTOR COUNTERS 2 CIRCUIT>Use the ZERO CIRCUIT command to reset circuit counters on the executor node.$ZERO  KNOWN CIRCUITS COUNTERS CIRCUIT circuit-id3 KNOWN CIRCUITS?Indicates that counters for all known circuits are to be reset.3 CIRCUIT circuit-idCIdentifies a particular circuit for which counters are to be reset.2 LINEFUse the ZERO LINE command to reset line counters on the executor node. ZERO KNOWN LINES COUNTERS LINE line-id 3 KNOWN LINES<Indicates that counters for all known lines are to be reset.3 LINE line-id@Identifies a particular line for which counters are to be reset.2 MODULEIntroduces a MODULE parameter.3 X25-PROTOCOL9Zero the counters for a particular DTE or all known DTES.AZERO MODULE X25-PROTOCOL DTE dte-addr NETWORK net-name COUNTERS4 KNOWN DTES KNOWN NETWORK4 DTE dte-addr/Zeroes the counters for the specified DTE only. 4 KNOWN DTES'Zeroes the counters for all known DTEs. 3 X25-SERVER,Zero the counters for the X.25 Call Handler.ZERO MODULE X25-SERVER COUNTERS 3 X29-SERVER,Zero the counters for the X.29 Call Handler.ZERO MODULE X29-SERVER COUNTERS2 NODE1Use the ZERO NODE command to reset node counters. ZERO KNOWN NODES COUNTERS NODE node-id 3 KNOWN NODES<Indicates that counters for all known nodes are to be reset.3 NODE node-id@Identifies a particular node for which counters are to be reset. 3 Examples! NCP>ZERO NODE TRNTO COUNTERS@ This command resets all node counters maintained on the- executor node for remote node TRNTO.!! end of NCPHELP.HLP!ww