% Librarian A09-30*5!"  5 ATTACHHCHECKCLEARCONVERT6CREATE!EXIT GET_TOWERS HELPLOAD$RECREATESPAWN PUsage  v1 HELP!GThe DECNET_LOC_REGISTER utility provides system managers with functions8to help manage node names in the DECdns local namespace.These functions aid in:I - Creating an initial local name file containing node information to be+ loaded into the DECdns local namespace.D - Recreating the local name file from the names that are currently) loaded in the DECdns local namespace.J - Getting the full tower sets for node definitions that have only simp le@ addresses defined, by directly querying the indicated nodes.E - Loading the information contained in the local name file into theH DECdns local namespace, using default tower sets when the real tower% set information is not available.L - Using the information contained in the local name file to register nodes( into a DECdns distributed namespace.I - Clearing all names from the DECdns local namespace when its use is no longer necessary.LUse the HELP command to obtain information on the functions provided by thisutility.! ww:̢1 Usage!JDECdns provides a local naming option for defining DECnet node names. TheBlocal namespace is accessible only from the node it is created on.! 2 Invocation!KThe DECNET_LOC_REGISTER utility is normally invoked using the RUN command. DIt can also be invoked using a foreign command symbol. For example:D $ RUN SYS$SYSTEM:DECNET_LOC_REGISTER !Invoke the utilityH $ LOCREG :== $SYS$SYSTEM:DECNET_LOC_REGISTER !Foreign command symbolD $ LOCREG !Invoke the utilityJIf a foreign command symbol is used, a command line can be passed directlyDto DECNET_LOC_REGISTER on the invocation command line. For example: $ LOCREG LOAD!2 Namespace_Setup!%To use the local namespace, you must:I 1) Use the CREATE command to create a local name file that describes theL nodes you need to register. This file contains node  name and addressing1 information for the nodes you need to access.G 2) Use the GET TOWERS command to obtain the full addressing tower setsF for any node definitions that have only simple addresses specifiedB (this is optional, and is used to help make network connection" establishment more efficient).G 3) Use the LOAD command to load the information contained in the localG name file into the DECdns local namespace. This makes the name and4 address information availa ble for use by DECnet.I 4) Use NET$CONFIGURE to set DECnet to use the DECdns local namespace, by, specifying LOCAL: as the namespace name.G 5) Edit the local name file, and use the GET TOWERS and LOAD commands,C whenever you need to add, change, or delete node definitions. !2 Adding_and_Removing!FTo change node information, you must edit the local name file and add,Imodify, or delete node definitions. A description of how to enter a nodeKdefinition is placed at the top of the file when it is first created. This"information should not be deleted.KWhen adding a new node to the text file, specify the addressing informationMeither as a simple address or as a partial DECnet-Plus addressing tower set. DSpecifying the tower set makes network connection establishment moreKefficient. If you do not know the tower set for a node, specify the simpleEPhase IV address or NET (network entity title) and use the GET TOWERS%command to obtain the real tower set.IOn ce the node (or nodes) has been added to or removed from the text file,Fuse the LOAD command to make the change to the DECdns local namespace.!2 Obtaining_Help!FThe HELP command allows you to obtain help for any command and commandoption.KWhile entering a command, you can also obtain the list of options availableJat that point in the command. To do this, type a question mark (?) at theGend of the command line. This lists the available command options, and,prompts you for the desired option (if any).! 2 Termination!HThe EXIT command causes DECNET_LOC_REGISTER to terminate execution. The(Ctrl/Z key combination can also be used.FIf a command was specified on the invocation command line, the utility7exits immediately after the command has been processed.! ww:̢1 CREATE!JThis creates an initial local name file that can be loaded into the DECdnslocal namespace. CREATE [file-name]LIf the DECnet Phase IV node data file (SYS$SYSTEM:NETNODE_REMOTE.DAT) existsHand is readable, the local name file is filled in with an initial set ofLnode definitions taken from this data file. If the data file does not existGor is not readable, the local name file is created with no initial node definitions.LIf you do not specify a file name in the CREATE command, a default file name6of SYS$SYSTEM:DECNET_LOC_NODE_DEFINITIONS.TXT is used.! ww:̢ 1 GET_TOWERS!IThis command gets the tower set for any node in the local name file which"has only a simple address defined. GET TOWERS [file-name] [ALL]KWhen you use CREATE to create an initial local name file, the addresses areJplaced in the file as simple Phase IV addresses. Similarly, when you editJthe local name file, you can specify the node addresses as simple Phase IVFaddresses or DECnet-Plus NETs (network entity titles). The GET TOWERSIcommand is used to obtain the full DECnet-Plus tower sets for these nodesby using the simple addresses.IThe GET TOWERS command scans the local name file for any node definitionsHthat contain an empty TOWERS parameter or no TOWERS parameter. For eachIsuch definition, it uses the ADDRESS parameter to attempt a connection toJthe specified node. If the connection succeeds, it obtains the real towerKset information from the node, and adds the appropriate TOWERS parameter toMthe node definition. If the connection fails, it leaves the TOWERS parameter9empty, allowing GET TOWERS to be retried a t a later date.FTo update the tower set information for some subset of the nodes, editDthe text file, delete the TOWERS parameter from the appropriate nodeIdefinitions, and issue the GET TOWERS command. The command obtains towerFinformation for only those node definitions that do not already have aTOWERS parameter specified.ITo update the tower set information for all nodes in the local name file,Lissue the GET TOWERS ALL command. The command obtains tower information forLall nodes listed in the file. If it cannot obtain tower information for anyEparticular node, it will leave the old tower information for the node unchanged.GUse of this command is optional. You can specify the tower set for anyJnode when you edit the local name file, or you can specify only the simpleDaddress. If you specify only the simple address, network connection/establishment might take longer for some nodes.FIf you do not specify a file name in the GET TOWERS command, a default@file name of SYS$SYSTEM:DECNET_LOC_NODE_DEFINITIONS.TXT is used.! ww:̢1 CHECK!KThis checks the local name file and the DECdns local namespace, and reportsHhow many nodes are defined in the file and how many can fit in the local namespace. CHECK [file-name]KIf you do not specify a file name in the CHECK command, a default file name6of SYS$SYSTEM:DECNET_LOC_NODE_DEFINITIONS.TXT is used.! ww:̢1 LOAD!IThis loads the information from the loca l name file into the DECdns local namespace. LOAD [file-name]EBefore loading the local name file, the LOAD command first clears allKcurrent names from the local namespace. It then reads each node definition.and registers the node in the local namespace.GFor each node definition it reads, the LOAD command checks for a TOWERSFparameter. If it finds one, it registers the node using the specifiedJtower set. If not, it registers the node using a default tower set. ThisIdefault tower set is based on the simple address specified in the ADDRESSKparameter, and on the node's DECnet phase specified in the PHASE parameter.JIf you do not specify a file name in the LOAD command, a default file name6of SYS$SYSTEM:DECNET_LOC_NODE_DEFINITIONS.TXT is used.! ww:̢ 1 RECREATE!IThis recreates a local name file from the information found in the DECdnsKlocal namespace. This is used if the local name file is lost or corrupted. RECREATE [file-name]KThe local name file is filled in with the set of node definitions that wereJpreviously loaded into the DECdns local namespace. If no node definitionsGcan be found in the DECdns local namespace, an empty local name file iscreated.IIf you do not specify a file name in the RECREATE command, a default file;name of SYS$SYSTEM:DECNET_LOC_NODE_DEFINITIONS.TXT is used.! ww:̢ 1 CONVERT!GThis converts the information in the local name file into a DCL commandEfile that can be used to register the nodes into a DECdns distributedHnamespace. This is generally done once before switching over to the useof a distributed namespace.0 CONVERT [text-file-name] TO script-file-nameGWhen converting the local name file to a registration command file, theLCONVERT command reads each node definition in the local name file and writes>a corresponding node registration command in the command file.JBefore executing the command file to register the nodes, it is recommendedLthat you edit the command file and verify that the proper namespace name andLdirectories are used. You can also change some of the optional registrationGcommand parameters. The registration command format and parameters aredescribed in the command file.IIf you do not specify a local name file in the CONVERT command, a default;name of SYS$SYSTEM:DECNET_LOC_NODE_DEFINITIONS.TXT is used.! ww:̢1 CLEAR!>This command clears all names from the DECdns local na mespace. CLEARGThis command is used to delete all names from the local namespace after0switching to the use of a distributed namespace.! ww1 SPAWN!FExecute a single DCL command in a subprocess, or create an interactive8subprocess in which you can enter multiple DCL commands. SPAWN [dcl-command]CIf you specify the optional DCL command, it is executed and control>returns to DECNET_LOC_REGISTER when the execution is complete.CIf you do not spec!ify the optional DCL command, you are placed in aFsubprocess and presented with the DCL prompt. When you log out of the3subprocess, control returns to DECNET_LOC_REGISTER.! ww1 ATTACH!IAttach the terminal to another process. This transfers control from yourGcurrent process to the specified process. The current process (running:DECNET_LOC_REGISTER.EXE) is placed in a hibernation state. ATTACH [process-name]JIf you specify the optional process name, the terminal is attached to thatLprocess. The SHOW PROCESS and SHOW SYSTEM commands can be used to determineprocess names.IIf you do not specify the optional process name, the terminal is attached6to the parent (owner) process for the current process.! ww1 EXIT!JExit the utility. The QUIT command or the Ctrl/Z key combination can alsobe used.ww