% Librarian A09-30l   50ADDAddress_TowersATTACH. DEREGISTER+DO+EXIT,TEXPORT~ Export_File HELP:IMPORTGMANAGEIMODIFY&Names_and_DirectoriesNSAP_AddressesPhase_IV_AddressestPhase_IV_PrefixesUREGISTER`tREMOVEhDRENAMEpREPAIRvRESETzSETSHOWpSPAWNUPDATE Usage   1 HELP!GThe DECNET_REGISTER utility provides network managers with functions toGhelp manage node names in the directory service or services used within the network.The functions are:G - Register node names, synonyms, and addresses in a directory service5 - Modify a node registration's synonym or addresses( - Add addresses to a node registration- - Remove addresses from a node registration@ - Show a node registration and verify its internal consistencyI  - Export node registration data from a directory service to a text fileK - Import node registration data from a text file into a directory serviceG - Update a node's registered address information from the node itself3 - Rename a registered node in a directory service. - Deregister a node from a directory service%The supported directory services are:7 Local Naming Database DECdns Phase IV Database! ww 1 Usage!@These sub-topics describe how to use the various features of theDECNET_REGISTER utility.! 2 Invocation!FThe DECNET_REGISTER utility is normally invoked using the RUN command.DIt can also be invoked using a foreign command symbol. For example:A $ RUN SYS$SYSTEM:DECNET_REGISTER !Invoke the utilityE $ NETREG :== $SYS$SYSTEM:DECNET_REGISTER !Foreign command symbolA $ NETREG !Invoke the utilityJIf a foreign command symbol is used, a command line can be passed directly@to DECNET_REGISTER on the invocation command line. For example: $ NETREG SHOW NODE MyNodeJIf the utility is invoked by a foreign command symbol with a command line,Fas shown above, it executes the command and exits after the command isDcomplete. If not, it continues to accept commands until an explicitexit command is issued.!! 2 Termination!DThe EXIT command causes DECNET_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.!2 Initialization_Command_File!BOn startup, the DECNET_REGISTER utility always attempts to execute?an initialization command file if one is present. This is most>useful for pre-setting the values to use for command parameter defaults.ADECNET_REGISTER checks for an initialization file using a defaultname of:! SYS$LOGIN:DECNET_REGISTER.INIEIf this file is fo und, it is automatically executed as a command fileEcontaining a series of DECNET_REGISTER commands. If a different fileGname is to be used, specify the file name using the logical definition:: $ DEFINE DECNET_REGISTER_INIT initialization-file-name:If this logical definition exists, #(NETREG_NAME) uses the7specified file name, rather than the default file name.!2 Interface_Modes!?After DECNET_REGISTER is invoked, and after it has executed the>initialization command file (i f any), it enters either commandline mode or forms mode.GCommand line mode is used if the utility is invoked from a command fileHor from a hardcopy terminal. In this case, the utility accepts commandsas described in this help file.CForms mode is used if the utility is invoked from a video terminal.BThe DECNET_REGISTER utility can be forced to always run in command@line mode or forms mode by using one of the logical definitions:G $ DEFINE DECNET_REGISTER_COMMANDS 1 !Force the u se of command lines? $ DEFINE DECNET_REGISTER_FORMS 1 !Force the use of formsAIf either of these is defined, DECNET_REGISTER uses the indicated0interface mode, regardless of how it is invoked.EThe DECNET_REGISTER utility can also be forced to run in command lineAmode or forms mode by supplying one of the following arguments onthe invocation command line:B $ NETREG /C !Force the use of command lines: $ NETREG /F !Force the use of formsGTo use these arguments, DECNET_REGISTER must be invoked using a foreigncommand symbol.?If supplied, these arguments override both the I/O mode and thelogical definitions.!2 Entering_Commands!?The following conventions are used in the command descriptions:C - Words presented in upper case are keywords that must be enteredE as shown. These can be entered using either upper or lower case,9 and can generally be abbreviated to three characters.C - Words presen ted in lower case represent values to be determined) by the user (node names for example).H - Words or phrases enclosed in square brackets ("[xxx]") are optional.G If these are not supplied, some default value or action is assumed.!2 Setting_Defaults!HDefault values are provided for most optional parameters. These defaultBvalues can be displayed and changed using the SHOW, SET, and RESETDEFAULT commands.FThe SET DEFAULT command can be used in an initialization file in orderFto provide the same default parameter values each time DECNET_REGISTERis run.!2 Obtaining_Help!FThe HELP command allows you to obtain help for any command and commandoption.JWhen 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, andFprompts you for the desired option (if any). At the prompt, enter the)option plus the rest of the command line.! ww 1 ADD!*Add address towers to a node registration. ADD [DECNET] NODE node-name TOWERS {tower-set}) [ DIRECTORY_SERVICE dir-service ]& [ PHASEIV_PREFIX addr-prefix ]* [ REVERSE_DIRECTORY rev-dir-name ]EThis is used when a new address tower is available on a node, and theHaddressing information needs to be added into the node registration in adirectory service.!2 NODE!BThis specifies the name of the node whose address towers are to be modified. NODE node-nameBThe node name must be the fully specified name for the node in the directory service. For example: For Local: NODE MailHub, For DECdns: NODE MyCo:.Sales.MailHub For Phase IV: NODE MLHUB!2 DIRECTORY_SERVICE!IThis specifies the directory service that contains the node registration.! DIRECTORY_SERVICE dir-serviceThe service must be one of: DIRECTORY_SERVICE LOCAL DIRECTORY_SERVICE DECDNS DIRECTORY_SERVICE PHASEIVHIf not specified, the default service type is used. This default can be<displayed or changed using the SHOW or SET DEFAULT commands.!2 TOWERS!GThis specifies the set of one or more address towers to add to the node registration. TOWERS {tower, tower, ...}-Each address tower in the set has the format: transport/addressEFields can be omitted from left to right, and assume a default value.F  Transport can be either TP4, TP4=tsel, or NSP, and defaults to NSPD if the N-Sel in the address field is "20", and to TP4 otherwise.D Address can be either an NSAP value or a Phase IV address value.D If a Phase IV address is specified, an NSAP is constructed usingC the specified address and the Phase IV prefix value. The N-Sel value is always "20".HAssuming that the Phase IV address prefix value is "49::", some examplesof address towers are:3 Abbreviation  Fully Specified3 ------------ ---------------> 1.5 NSP/49::01:AA0004000504:20A 1.5+39:840 NSP/39:840:01:AA0004000504:20A 39:840:01:AA0004000504:20 NSP/39:840:01:AA0004000504:20F 39:840:01:AA0004000504:21 TP4=DEC0/39:840:01:AA0004000504:21F TP4/39:840:01:AA0004000504:21 TP4=DEC0/39:840:01:AA0004000504:21CExamples of address towers using normal default values for a DECnet2Phase IV node and for a DECnet-Plus node might be: TOWERS={1.5}E TOWERS={2.54, 39:840:01:080043A751F4:20, 39:840:01:080043A751F4:21}BSee the ADDRESS_TOWERS topic for details about the address towers.!2 PHASEIV_PREFIX!CThis specifies the AFI, IDI, and preDSP to use when constructing anFNSAP from a Phase IV address. This is used when a Phase IV address isspecified in an address tower. PHASEIV_PREFIX addr-prefix For example:/ TOWERS {1.5} PHASEIV_PREFIX 39:840:800AB738Iresults in the following NSAP being used to represent the DECnet Phase IVaddress:- 39:840:800AB738-0001:AA-00-04-00-05-04:20'An alternate way of expressing this is: TOWERS {1.5+39:840:800AB738}DThe advantage of using the PHASEIV_PREFIX method is that the addressCprefix is applied to all Phase IV addresses without being specifiedmultiple times.DIf not specified, the default Phase IV prefix is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.ISee the PHASE_IV_PREFIXES topic for details about Phase IV prefix values.!2 REVERSE_DIRECTORY!DThis specifies the base directory or name entry to use when creatingCthe reverse address mapping links to the node name (also called theback translation links)." REVERSE_DIRECTORY rev-dir-nameCThe links under this directory are used to map NSAP values to theirFrespective node names. These directories are used only for the DECdnsdirectory service.FIf not specified, the default reverse directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.HSee the NAMES_AND_DIRECTORIES topic for more information on directories.!! ww 1 ATTACH!IAttach the terminal to another process. This transfers control from yourGcurrent process to the specified process. The current process (running6DECNET_REGISTER.EXE) is placed in a hibernation state. ATTACH [process-name]EIf you specify the optional process name, the terminal is attached toGthat process. The SHOW PROCESS and SHOW SYSTEM commands can be used todetermine process names.IIf you do not specify the optional process name, the terminal is attached6to the parent (owner) process for the current process.! ww  1 DEREGISTER!4Remove a node registration from a directory service.$ DEREGISTER [DECNET] NODE node-id) [ DIRECTORY_SERVICE dir-service ]& [ PHASEIV_PREFIX addr-pref!ix ]* [ REVERSE_DIRECTORY rev-dir-name ]* [ SYNONYM_DIRECTORY syn-dir-name ]GThis is used when a node is no longer available in the network, and the?node registration needs to be removed from a directory service.!2 NODE!BThis specifies the identification of the node to be de-registered. NODE node-id&The node identification can be one of:C The fully specified name for the node in the directory service.& The Phase IV synonym for the node.2 One of" the NET or NSAP addresses for the node.E The Phase IV address (and optional Phase IV prefix) for the node.-Wildcards are allowed in names and addresses.!3 Names!DThe node to be de-registered can be specified using its full name orits Phase IV synonym.EThe syntax of a fully specified name depends on the directory service8being used. Examples of fully specified names might be: For Local: NODE MailHub, For DECdns: NODE MyCo:.Sales.MailHub For Phase IV#: NODE MLHUB?An example of a Phase IV synonym for any of the above might be: NODE MLHUBBWildcards are allowed in the node name using an asterisk (*). Forexample: For Local: NODE Mail** For DECdns: NODE MyCo:.Sales.Mail* For Phase IV: NODE ML*FThe wildcard character can come anywhere in the last part of the name.,Only a single wildcard character is allowed.! 3 Addresses!GThe node to be de-registered can be specified using one of its NETs (or $NSAPs), or its Phase IV address.GAn NET is an NSAP address value with an N-Sel value of "00" (indicatingEthat it is independent of the type of transport service in use on theGnode). If you specify an NSAP instead of an NET, it is converted to anNET before it is used.9 DNA format: ::-::005 OSI format: +00Examples of NETs might be:4 DNA format: NODE 39:840:0001:AA-00-04-00-05-04:00, OSI format: NODE 39%840+0001AA000400050400GIf the node has a Phase IV address, that can be used instead of an NET. Format: .' .+HThis is internally converted to an NET, using the Phase IV prefix value.GThe Phase IV prefix value can be specified with the Phase IV address orCthe PHASEIV_PREFIX parameter, or set using the SET DEFAULT command.(Examples of a Phase IV address might be:E NODE 1.5 Uses the default Phase IV p &refixE NODE 1.5+39:840 Uses an explicit Phase IV prefixE NODE 1.5 PHASEIV_PREFIX 39:840 Uses an explicit Phase IV prefixGWildcards are allowed in the NET or Phase IV address using an asterisk.DThe wildcard character must replace either the node id, or the localGarea and the node id. For an NET containing a wildcard, do not specifyan N-Sel value.9 39:840:0001:* (or 39840+0001*) Wildcard the node idH 39:840:* (or 39840+*) Wildcard the loca'l area and node id9 1.* Wildcard the node idB *.* Wildcard the area and node id!2 DIRECTORY_SERVICE!IThis specifies the directory service that contains the node registration.! DIRECTORY_SERVICE dir-serviceThe service must be one of: DIRECTORY_SERVICE LOCAL DIRECTORY_SERVICE DECDNS DIRECTORY_SERVICE PHASEIVHIf not specified, the default service type is used. This default can be<displayed (or changed using the SHOW or SET DEFAULT commands.!2 PHASEIV_PREFIX!CThis specifies the AFI, IDI, and preDSP to use when constructing anGNET from a Phase IV address. This is used only when a Phase IV addressis specified for the node id. PHASEIV_PREFIX addr-prefixGAn alternate form is to add the Phase IV prefix to the Phase IV addressspecification.For example, both:+ NODE 1.5 PHASEIV_PREFIX 39:840:800AB738 NODE 1.5+39:840:800AB738Gresult in the following NE)T being used to represent the DECnet Phase IVaddress:- 39:840:800AB738-0001:AA-00-04-00-05-04:00HIf not specified, the default Phase IV prefix is used. This default can?be displayed or changed using the SHOW or SET DEFAULT commands.ISee the PHASE_IV_PREFIXES topic for details about Phase IV prefix values.!2 REVERSE_DIRECTORY!DThis specifies the base directory or name entry to use when deletingCthe reverse address mapping links to the node name (also called theback tra*nslation links)." REVERSE_DIRECTORY rev-dir-nameCThe links under this directory are used to map NSAP values to theirFrespective node names. These directories are used only for the DECdnsdirectory service.FIf not specified, the default reverse directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.HSee the NAMES_AND_DIRECTORIES topic for more information on directories.!2 SYNONYM_DIRECTORY!DThis specifies the base directory or + name entry to use when deleting*the synonym mapping link to the node name." SYNONYM_DIRECTORY syn-dir-nameCThe links under this directory are used to map Phase IV synonyms toEtheir respective node names. These directories are used only for theDECdns directory service.FIf not specified, the default synonym directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.HSee the NAMES_AND_DIRECTORIES topic for more information on directories.,! wwH9 1 DO!CExecute a named command file containing commands to #(NETREG_NAME). DO command file%An alternate form if this command is: @command fileAThe commands in the command file must appear as if entered at theA"DECNET_REGISTER>" prompt. A #(COMMAND_FILE) can reference othercommand files.DCommands are processed in order until the end of the file or until acommand error occurs.! wwH9 1 EXIT!AExit the utility. - The QUIT command or the Ctrl/Z key combinationcan also be used.! wwH9 1 EXPORT!HExtract node registration information for some set of nodes and write itto a text file.5 EXPORT [DECNET] NODE node-id FILE data-file-name) [ DIRECTORY_SERVICE dir-service ]& [ PHASEIV_PREFIX addr-prefix ]* [ REVERSE_DIRECTORY rev-dir-name ]* [ SYNONYM_DIRECTORY syn-dir-name ]# [ NSAP_FORMAT addr-format ]2Once the information has been ex .ported, it can be:7 - Used for reporting or database maintenance purposes.D - Used to make network-wide changes, such as modifying the NSAP IDPF value, by editing the text file and using the MODIFY feature of the IMPORT command.G - Used to move node information from one directory service to another,I using the REGISTER, UPDATE, or REPLACE features of the IMPORT command.B - Used to verify that the addressing information in one directoryH service is the same as in another dir/ectory service, using the VERIFY! feature of the IMPORT command.F - Used to remove node information from a directory service, using the, DEREGISTER feature of the IMPORT command.!2 NODE!>This specifies the identification of the nodes to be exported. NODE node-id&The node identification can be one of:C The fully specified name for the node in the directory service.& The Phase IV synonym for the node.2 One of the NET or NSAP addresses for the node.E The Ph0ase IV address (and optional Phase IV prefix) for the node.-Wildcards are allowed in names and addresses.!3 Names!CThe node to be exported can be specified using its full name or itsPhase IV synonym.EThe syntax of a fully specified name depends on the directory service8being used. Examples of fully specified names might be: For Local: NODE MailHub, For DECdns: NODE MyCo:.Sales.MailHub For Phase IV: NODE MLHUB?An example of a Phase IV synonym for a1ny of the above might be: NODE MLHUBBWildcards are allowed in the node name using an asterisk (*). Forexample: For Local: NODE Mail** For DECdns: NODE MyCo:.Sales.Mail* For Phase IV: NODE ML*FThe wildcard character can come anywhere in the last part of the name.,Only a single wildcard character is allowed.! 3 Addresses!BThe node to be exported can be specified using one of its NETs (or NSAPs), or its Phase IV address.GAn NET is an NSAP address 2value with an N-Sel value of "00" (indicatingEthat it is independent of the type of transport service in use on theGnode). If you specify an NSAP instead of an NET, it is converted to anNET before it is used.9 DNA format: ::-::005 OSI format: +00Examples of NETs might be:4 DNA format: NODE 39:840:0001:AA-00-04-00-05-04:00, OSI format: NODE 39840+0001AA000400050400GIf the node has a Phase IV address, 3that can be used instead of an NET. Format: .' .+HThis is internally converted to an NET, using the Phase IV prefix value.GThe Phase IV prefix value can be specified with the Phase IV address orCthe PHASEIV_PREFIX parameter, or set using the SET DEFAULT command.(Examples of a Phase IV address might be:C NODE 1.5 !Uses the default Phase IV prefixC NODE 1.5+39:840 !Uses an explicit Phas 4e IV prefixC NODE 1.5 PHASEIV_PREFIX 39:840 !Uses an explicit Phase IV prefixGWildcards are allowed in the NET or Phase IV address using an asterisk.DThe wildcard character must replace either the node id, or the localGarea and the node id. For an NET containing a wildcard, do not specifyan N-Sel value.9 39:840:0001:* (or 39840+0001*) Wildcard the node idH 39:840:* (or 39840+*) Wildcard the local area and node id9 1.* Wildcard 5the node idB *.* Wildcard the area and node id!2 FILE!@This specifies the name of the text file to contain the exported information. FILE data-file-nameASee the EXPORT_FILE topic for more information on the contents of this file.!2 DIRECTORY_SERVICE!IThis specifies the directory service that contains the node registration.! DIRECTORY_SERVICE dir-serviceThe service must be one of: DIRECTORY_SERVICE LOCAL DIRECT6ORY_SERVICE DECDNS DIRECTORY_SERVICE PHASEIVHIf not specified, the default service type is used. This default can be<displayed or changed using the SHOW or SET DEFAULT commands.!2 PHASEIV_PREFIX!CThis specifies the AFI, IDI, and preDSP to use when constructing anGNET from a Phase IV address. This is used only when a Phase IV addressis specified for the node id. PHASEIV_PREFIX addr-prefixGAn alternate form is to add the Phase IV prefix to the Phase IV addressspecif7ication. For example:+ NODE 1.5 PHASEIV_PREFIX 39:840:800AB738 NODE 1.5+39:840:800AB738Bwould both result in the following NET being used to represent theDECnet Phase IV address:- 39:840:800AB738-0001:AA-00-04-00-05-04:00HIf not specified, the default Phase IV prefix is used. This default can?be displayed or changed using the SHOW or SET DEFAULT commands.ISee the PHASE_IV_PREFIXES topic for details about Phase IV prefix values.!2 REVERSE_DIRECTORY!EThis s 8pecifies the base directory or name entry to use when exportingCthe reverse address mapping links to the node name (also called theback translation links)." REVERSE_DIRECTORY rev-dir-nameCThe links under this directory are used to map NSAP values to theirFrespective node names. These directories are used only for the DECdnsdirectory service.FIf not specified, the default reverse directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.9HSee the NAMES_AND_DIRECTORIES topic for more information on directories.!2 SYNONYM_DIRECTORY!EThis specifies the base directory or name entry to use when exporting*the synonym mapping link to the node name." SYNONYM_DIRECTORY syn-dir-nameCThe links under this directory are used to map Phase IV synonyms toEtheir respective node names. These directories are used only for theDECdns directory service.FIf not specified, the default synonym directory is used. This default:Ccan be displayed or changed using the SHOW or SET DEFAULT commands.HSee the NAMES_AND_DIRECTORIES topic for more information on directories.! 2 NSAP_FORMAT!HThis specified the format to use when converting NSAP addresses to their,text representation in the export text file. NSAP_FORMAT DNA NSAP_FORMAT OSI.This causes the appropriate format to be used:? DNA format: ::-::; OSI format: +GIf not specified, the default NSAP format is used. This default can be<displayed or changed using the SHOW or SET DEFAULT commands.!! ww _ 1 IMPORT!EUses exported node registration information, contained in a text fileCcreated by the EXPORT command or by a text editor, to help maintaina directory service. IMPORT FILE data-file-name [ function ]& [ ERROR_FILE error-file-name ]" [ NAME_TEMPLATE template ]) [ DIRE<CTORY_SERVICE dir-service ]& [ PHASEIV_PREFIX addr-prefix ]* [ REVERSE_DIRECTORY rev-dir-name ]* [ SYNONYM_DIRECTORY syn-dir-name ]!2 FILE!?This specifies the name of the text file that contains the nodeinformation to import. FILE data-file-nameASee the EXPORT_FILE topic for more information on the contents of this file.! 2 Functions!%The following functions are provided.B IMPORT REGISTER - Register the listed nodes into the specified( = directory service.E IMPORT MODIFY - Make bulk changes to the nodes in the directoryC service. This provides a way to make a largeE number of synonym or tower changes at one time.B IMPORT UPDATE - Register the listed nodes into the directoryE service if they do not already exist, or modifyD them if they do exist. This provides a way toD make changes i >n one directory service based on? information in another directory service.E IMPORT REPLACE - Deregister any nodes that use the same synonymsF or towers as the listed nodes, and then registerH the listed nodes into the directory service. thisC provides a way to make a large number of name* changes at one time.A IMPORT VERIFY - Check whether or not the information in theA ? directory service matches the listed nodes.D IMPORT DEREGISTER - Deregister the listed nodes from the directory service.JIf no IMPORT function is specified, the IMPORT UPDATE function is assumed.! 2 ERROR_FILE!AThis specifies the name of the file to receive any error reports. ERROR_FILE error-file-nameCAn error file is useful since the IMPORT command is performing bulk>operations that can result in errors scrolling off the screen.@GErrors are written into the file as comments, followed by the line fromGthe input file that caused the error. This allows you to use the errorFfile as an IMPORT input file, after correcting the errors. Using thisImethod, only those operations that resulted in an error will be re-tried.4If not specified, all errors are sent to the screen.!2 NAME_TEMPLATE!HThis specifies how the "name" field in the export file node registrationinformation is used. NAME_TEMPLATE template AGThe node registration information contained in the export file includesJeach node's terminating name. This is generally the part of the name thatHis the same regardless of the directory service. For example, "MailHub"*is the terminating name for the following: Local: MailHub# DECdns: MyCo:.Sales.MailHubFTo convert a terminating name to a fully specified name for the targetCdirectory service, it is combined with the name template. The nameGtemplate is a string tha Bt indicates what the fully specified name is toElook like, with an asterisk (*) where the terminating name goes. Forexample: Local: * DECdns: MyCo:.Sales.*FIf not specified, the name template defined in the export file for theHtarget directory service is used. If the export file does not contain aDvalid name template for the target directory service, errors result.GSee the EXPORT_FILE topic for descriptions of the name template control1line and the node registraCtion information lines.!2 DIRECTORY_SERVICE!DThis specifies the target directory service for the import function.! DIRECTORY_SERVICE dir-serviceThe service must be one of: DIRECTORY_SERVICE LOCAL DIRECTORY_SERVICE DECDNS DIRECTORY_SERVICE PHASEIVHIf not specified, the default service type is used. This default can be<displayed or changed using the SHOW or SET DEFAULT commands.!2 PHASEIV_PREFIX!CThis specifies the AFI, IDI, and preDSP to use when Dconstructing anFNSAP from a Phase IV address. This is used when a Phase IV address isspecified in an address tower. PHASEIV_PREFIX addr-prefix For example:" PHASEIV_PREFIX 39:840:800AB738IIf not specified, the Phase IV prefix defined in the export file is used.FIf the export file does not contain a Phase IV prefix definition, then>the Phase IV prefix set using the SET DEFAULT command is used.JSee the PHASE_IV_PREFIXES topic for details about Phase IV prefix values. JSee thEe EXPORT_FILE topic for a description of the Phase IV prefix controlline.!2 REVERSE_DIRECTORY!DThis specifies the base directory or name entry to use when creatingCreverse address mapping links for a node name (also called the backtranslation links)." REVERSE_DIRECTORY rev-dir-nameCThe links under this directory are used to map NSAP values to theirFrespective node names. These directories are used only for the DECdnsdirectory service.CIf not specified, the reverse ad Fdress directory name defined in theCexport file is used. If the export file does not contain a reverseCaddress directory name definition for the target directory service,Dthen the reverse directory name set using the SET DEFAULT command isused.FFor more information, please refer to the NAMES_AND_DIRECTORIES topic.BSee the EXPORT_FILE topic for a description of the reverse addressdirectory control line.!2 SYNONYM_DIRECTORY!DThis specifies the base directory or name entry to u Gse when creating&synonym mapping links for a node name." SYNONYM_DIRECTORY syn-dir-nameCThe links under this directory are used to map Phase IV synonyms toEtheir respective node names. These directories are used only for theDECdns directory service.GIf not specified, the synonym directory name defined in the export fileFis used. If the export file does not contain a synonym directory nameGdefinition for the target directory service, then the synonym directory/name set using tHhe SET DEFAULT command is used.FFor more information, please refer to the NAMES_AND_DIRECTORIES topic.DSee the EXPORT_FILE topic for a description of the synonym directory control line.!! ww _ 1 MANAGE!HExecute the appropriate management procedure for the specified directoryservice.* MANAGE [DIRECTORY_SERVICE dir-service]FThe management procedures only provides management of those aspects ofEthe directory service that affect how node names are stored anId used.EThey do not provide general management of the directory service. TheGspecific management functions provided depend on the directory service.DThe management procedure is executed as a child process, and control:returns to DECNET_REGISTER when the execution is complete.!2 DIRECTORY_SERVICE!3This specifies the directory service to be managed.! DIRECTORY_SERVICE dir-serviceThe service must be one of: DIRECTORY_SERVICE DECDNSEThe Local and Phase IV databasJes do not require any directory serviceEmanagement functions. This command does not apply to these directory services.HIf not specified, the default service type is used. This default can be<displayed or changed using the SHOW or SET DEFAULT commands.! ww _ 1 MODIFY!IChange a node's registered address tower or Phase IV synonym information." MODIFY [DECNET] NODE node-name) [ DIRECTORY_SERVICE dir-service ] [ SYNONYM synonym-name ] K[ TOWERS {tower-set} ]& [ PHASEIV_PREFIX addr-prefix ]* [ REVERSE_DIRECTORY rev-dir-name ]* [ SYNONYM_DIRECTORY syn-dir-name ]EThis command is used when the registered information for a node needsto be changed.!2 NODE!BThis specifies the name of the node whose address towers are to be modified. NODE node-nameBThe node name must be the fully specified name for the node in the directory service. For example: For Local: NODE MailHub, FoLr DECdns: NODE MyCo:.Sales.MailHub For Phase IV: NODE MLHUB!2 DIRECTORY_SERVICE!IThis specifies the directory service that contains the node registration.! DIRECTORY_SERVICE dir-serviceThe service must be one of: DIRECTORY_SERVICE LOCAL DIRECTORY_SERVICE DECDNS DIRECTORY_SERVICE PHASEIVHIf not specified, the default service type is used. This default can be<displayed or changed using the SHOW or SET DEFAULT commands.! 2 SYNONYM!FThis s Mpecifies a new Phase IV synonym for the node. This replaces anyBcurrent Phase IV synonym value in the node registration. Phase IVIsynonyms can be used in place of fully specified node names, particularly6with applications that do not support full node names. SYNONYM synonym-nameIThe synonym must be from 1 to 6 letters (A to Z) or digits (0 to 9), withGat least one letter. To specify that the node has no Phase IV synonym,Iuse two quotation marks ("") for the Phase IV synonym name. N For example: SYNONYM MLHUB SYNONYM ""GIf the SYNONYM parameter is not specified, the current synonym name forthe node is not modified.!2 TOWERS!AThis specifies the set of one or more address towers for the nodeAregistration. This replaces any current tower information in thenode registration. TOWERS {tower, tower, ...}-Each address tower in the set has the format: transport/addressEFields can be omitted from left to right, and assume a defaultO value.F Transport can be either TP4, TP4=tsel, or NSP, and defaults to NSPD if the N-Sel in the address field is "20", and to TP4 otherwise.D Address can be either an NSAP value or a Phase IV address value.D If a Phase IV address is specified, an NSAP is constructed usingC the specified address and the Phase IV prefix value. The N-Sel value is always "20".HAssuming that the Phase IV address prefix value is "49::", some examplesof address towers are:3 Abbrevia Ption Fully Specified3 ------------ ---------------> 1.5 NSP/49::01:AA0004000504:20A 1.5+39:840 NSP/39:840:01:AA0004000504:20A 39:840:01:AA0004000504:20 NSP/39:840:01:AA0004000504:20F 39:840:01:AA0004000504:21 TP4=DEC0/39:840:01:AA0004000504:21F TP4/39:840:01:AA0004000504:21 TP4=DEC0/39:840:01:AA0004000504:21CExamples of address towers using normal default values for a DQECnet2Phase IV node and for a DECnet-Plus node might be: TOWERS={1.5}E TOWERS={2.54, 39:840:01:080043A751F4:20, 39:840:01:080043A751F4:21}GTo specify that the node has no towers, supply an empty tower set. Forexample: TOWERS={}HIf the TOWERS parameter is not specified, the current address towers forthe node are not modified.BSee the ADDRESS_TOWERS topic for details about the address towers.!2 PHASEIV_PREFIX!CThis specifies the AFI, IDI, and preDSP to use when coRnstructing anCNSAP from a Phase IV address. This is used when a Phase IV address!is specified in an address tower. PHASEIV_PREFIX addr-prefix For example:/ TOWERS {1.5} PHASEIV_PREFIX 39:840:800AB738Ewould result in the following NSAP being used to represent the DECnetPhase IV address:- 39:840:800AB738-0001:AA-00-04-00-05-04:20-An alternate way of expressing this would be: TOWERS {1.5+39:840:800AB738}DThe advantage of using the PHASEIV_PREFIX method is Sthat the addressCprefix is applied to all Phase IV addresses without being specifiedmultiple times.HIf not specified, the default Phase IV prefix is used. This default can?be displayed or changed using the SHOW or SET DEFAULT commands.ISee the PHASE_IV_PREFIXES topic for details about Phase IV prefix values.!2 REVERSE_DIRECTORY!DThis specifies the base directory or name entry to use when creatingCthe reverse address mapping links to the node name (also called theback transTlation links)." REVERSE_DIRECTORY rev-dir-nameCThe links under this directory are used to map NSAP values to theirFrespective node names. These directories are used only for the DECdnsdirectory service.FIf not specified, the default reverse directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.FFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!2 SYNONYM_DIRECTORY!DThis specifies the base directory or namUe entry to use when creating*the synonym mapping link to the node name." SYNONYM_DIRECTORY syn-dir-nameCThe links under this directory are used to map Phase IV synonyms toEtheir respective node names. These directories are used only for theDECdns directory service.FIf not specified, the default synonym directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.FFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!V! ww  1 REGISTER!/Add a node registration to a directory service.$ REGISTER [DECNET] NODE node-name) [ DIRECTORY_SERVICE dir-service ] [ SYNONYM synonym-name ] [ TOWERS {tower-set} ]& [ PHASEIV_PREFIX addr-prefix ]* [ REVERSE_DIRECTORY rev-dir-name ]* [ SYNONYM_DIRECTORY syn-dir-name ]FThis is used when a new node is made available in the network, and theCnode registration needs to be added to a directory service tWo allowlookup by other nodes.!2 NODE!9This specifies the name of the new node to be registered. NODE node-nameBThe node name must be the fully specified name for the node in the directory service. For example: For Local: NODE MailHub, For DECdns: NODE MyCo:.Sales.MailHub For Phase IV: NODE MLHUB!2 DIRECTORY_SERVICE!EThis specifies the directory service the node is to be registered in.! DIRECTORY_SERVICE dir-serviceThe service muXst be one of: DIRECTORY_SERVICE LOCAL DIRECTORY_SERVICE DECDNS DIRECTORY_SERVICE PHASEIVHIf not specified, the default service type is used. This default can be<displayed or changed using the SHOW or SET DEFAULT commands.! 2 SYNONYM!DThis specifies the Phase IV synonym for the node. Phase IV synonymsEcan be used in place of fully specified node names, particularly with1applications that do not support full node names. SYNONYM synonym-nameIThe synonym muYst be from 1 to 6 letters (A to Z) or digits (0 to 9), withIat least one letter. To explicitly specify that the node has no Phase IVIsynonym, use two quotation marks ("") for the Phase IV synonym name. Forexample: SYNONYM MLHUB SYNONYM ""@If the SYNONYM parameter is not specified, a synonym name is notregistered for the node.!2 TOWERS!BThis specifies the set of one or more address towers for the node. TOWERS {tower, tower, ...}-Each address tower in the seZt has the format: transport/addressEFields can be omitted from left to right, and assume a default value.F Transport can be either TP4, TP4=tsel, or NSP, and defaults to NSPD if the N-Sel in the address field is "20", and to TP4 otherwise.D Address can be either an NSAP value or a Phase IV address value.D If a Phase IV address is specified, an NSAP is constructed usingC the specified address and the Phase IV prefix value. The N-Sel value is always "20".H [Assuming that the Phase IV address prefix value is "49::", some examplesof address towers are:3 Abbreviation Fully Specified3 ------------ ---------------> 1.5 NSP/49::01:AA0004000504:20A 1.5+39:840 NSP/39:840:01:AA0004000504:20A 39:840:01:AA0004000504:20 NSP/39:840:01:AA0004000504:20F 39:840:01:AA0004000504:21 TP4=DEC0/39:840:01:AA0004000504:21F TP4/39:840:01:AA00040005\04:21 TP4=DEC0/39:840:01:AA0004000504:21CExamples of address towers using normal default values for a DECnet2Phase IV node and for a DECnet-Plus node might be: TOWERS={1.5}E TOWERS={2.54, 39:840:01:080043A751F4:20, 39:840:01:080043A751F4:21}HTo explicitly specify that the node has no towers, supply an empty towerset. For example: TOWERS={}FIf the TOWERS parameter is not specified, no towers are registered for the node.BSee the ADDRESS_TOWERS topic for details about] the address towers.!2 PHASEIV_PREFIX!CThis specifies the AFI, IDI, and preDSP to use when constructing anCNSAP from a Phase IV address. This is used when a Phase IV address!is specified in an address tower. PHASEIV_PREFIX addr-prefix For example:/ TOWERS {1.5} PHASEIV_PREFIX 39:840:800AB738Ewould result in the following NSAP being used to represent the DECnetPhase IV address:- 39:840:800AB738-0001:AA-00-04-00-05-04:20-An alternate way of expressing this ^would be: TOWERS {1.5+39:840:800AB738}DThe advantage of using the PHASEIV_PREFIX method is that the addressCprefix is applied to all Phase IV addresses without being specifiedmultiple times.HIf not specified, the default Phase IV prefix is used. This default can?be displayed or changed using the SHOW or SET DEFAULT commands.ISee the PHASE_IV_PREFIXES topic for details about Phase IV prefix values.!2 REVERSE_DIRECTORY!DThis specifies the base directory or name entry _to use when creatingCthe reverse address mapping links to the node name (also called theback translation links)." REVERSE_DIRECTORY rev-dir-nameCThe links under this directory are used to map NSAP values to theirFrespective node names. These directories are used only for the DECdnsdirectory service.FIf not specified, the default reverse directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.FFor more information, please refer to th`e NAMES_AND_DIRECTORIES topic.!2 SYNONYM_DIRECTORY!DThis specifies the base directory or name entry to use when creating*the synonym mapping link to the node name." SYNONYM_DIRECTORY syn-dir-nameCThe links under this directory are used to map Phase IV synonyms toEtheir respective node names. These directories are used only for theDECdns directory service.FIf not specified, the default synonym directory is used. This defaultCcan be displayed or changed using the SHOW or aSET DEFAULT commands.FFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!! wwX 1 REMOVE!/Remove address towers from a node registration." REMOVE [DECNET] NODE node-name TOWERS {tower-set}) [ DIRECTORY_SERVICE dir-service ]& [ PHASEIV_PREFIX addr-prefix ]* [ REVERSE_DIRECTORY rev-dir-name ]HThis is used when an address tower is no longer available on a node, andIthe addressing information needs to be remboved from the node registrationin a directory service.!2 NODE!BThis specifies the name of the node whose address towers are to be modified. NODE node-nameBThe node name must be the fully specified name for the node in the directory service. For example: For Local: NODE MailHub, For DECdns: NODE MyCo:.Sales.MailHub For Phase IV: NODE MLHUB!2 DIRECTORY_SERVICE!IThis specifies the directory service that contains the node registration.! c DIRECTORY_SERVICE dir-serviceThe service must be one of: DIRECTORY_SERVICE LOCAL DIRECTORY_SERVICE DECDNS DIRECTORY_SERVICE PHASEIVHIf not specified, the default service type is used. This default can be<displayed or changed using the SHOW or SET DEFAULT commands.!2 TOWERS!GThis specifies the set of one or more address towers to remove from thenode registration. TOWERS {tower, tower, ...}-Each address tower in the set has the format: transp dort/addressEFields can be omitted from left to right, and assume a default value.F Transport can be either TP4, TP4=tsel, or NSP, and defaults to NSPD if the N-Sel in the address field is "20", and to TP4 otherwise.D Address can be either an NSAP value or a Phase IV address value.D If a Phase IV address is specified, an NSAP is constructed usingC the specified address and the Phase IV prefix value. The N-Sel value is always "20".HAssuming that the Phase IV addre ess prefix value is "49::", some examplesof address towers are:3 Abbreviation Fully Specified3 ------------ ---------------> 1.5 NSP/49::01:AA0004000504:20A 1.5+39:840 NSP/39:840:01:AA0004000504:20A 39:840:01:AA0004000504:20 NSP/39:840:01:AA0004000504:20F 39:840:01:AA0004000504:21 TP4=DEC0/39:840:01:AA0004000504:21F TP4/39:840:01:AA0004000504:21 TP4=DEC0/39:840:01:AA0f004000504:21CExamples of address towers using normal default values for a DECnet2Phase IV node and for a DECnet-Plus node might be: TOWERS={1.5}E TOWERS={2.54, 39:840:01:080043A751F4:20, 39:840:01:080043A751F4:21}BSee the ADDRESS_TOWERS topic for details about the address towers.!2 PHASEIV_PREFIX!CThis specifies the AFI, IDI, and preDSP to use when constructing anFNSAP from a Phase IV address. This is used when a Phase IV address isspecified in an address tower. PHASgEIV_PREFIX addr-prefix For example:/ TOWERS {1.5} PHASEIV_PREFIX 39:840:800AB738Ewould result in the following NSAP being used to represent the DECnetPhase IV address:- 39:840:800AB738-0001:AA-00-04-00-05-04:20-An alternate way of expressing this would be: TOWERS {1.5+39:840:800AB738}DThe advantage of using the PHASEIV_PREFIX method is that the addressCprefix is applied to all Phase IV addresses without being specifiedmultiple times.HIf not specified, the hdefault Phase IV prefix is used. This default can?be displayed or changed using the SHOW or SET DEFAULT commands.ISee the PHASE_IV_PREFIXES topic for details about Phase IV prefix values.!2 REVERSE_DIRECTORY!DThis specifies the base directory or name entry to use when deletingCthe reverse address mapping links to the node name (also called theback translation links)." REVERSE_DIRECTORY rev-dir-nameCThe links under this directory are used to map NSAP values to theirFrespiective node names. These directories are used only for the DECdnsdirectory service.FIf not specified, the default reverse directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.FFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!! ww 1 RENAME!=Change the registered name for a node in a directory service.= RENAME [DECNET] NODE old-node-name NEW_NAME new-node-name) [ DIRECTORY_SERV jICE dir-service ]$ [ SYNONYM new-synonym-name ]* [ REVERSE_DIRECTORY rev-dir-name ]* [ SYNONYM_DIRECTORY syn-dir-name ]GThis is used when a node's name has been changed, and that change needsDto be reflected in a directory service. The attribute values stored under the name remain unchanged.ENodes can be renamed only within a directory service. They cannot be6renamed from one type of directory service to another.JThis function only changes the name in the direcktory service, and does notGdirectly affect the name on the node itself. To change the name on the3node, use the node's network configuration utility.!2 NODE!2This specifies the name of the node to be renamed. NODE old-node-nameBThe node name must be the fully specified name for the node in the directory service. For example: For Local: NODE MailHub, For DECdns: NODE MyCo:.Sales.MailHub For Phase IV: NODE MLHUB! 2 NEW_NAME!)This specifies thel new name for the node. NEW_NAME new-node-nameDThe new node name must be a fully specified name for the node in the directory service. For example: For Local: NODE MailHub, For DECdns: NODE MyCo:.Sales.MailHub For Phase IV: NODE MLHUB!2 DIRECTORY_SERVICE!JThis specifies the directory service that contains the node to be renamed.! DIRECTORY_SERVICE dir-serviceThe service must be one of: DIRECTORY_SERVICE LOCAL DIRECTORY_SERVICE mDECDNS DIRECTORY_SERVICE PHASEIVHIf not specified, the default service type is used. This default can be<displayed or changed using the SHOW or SET DEFAULT commands.! 2 SYNONYM!HThis specifies the new Phase IV synonym for the node. Phase IV synonymsEcan be used in place of fully specified node names, particularly with1applications that do not support full node names. SYNONYM new-synonym-nameIThe synonym must be from 1 to 6 letters (A to Z) or digits (0 to 9), withInat least one letter. To explicitly specify that the node has no Phase IVIsynonym, use two quotation marks ("") for the Phase IV synonym name. Forexample: SYNONYM MLHUB SYNONYM ""GIf the SYNONYM parameter is not specified, the previous synonym name is retained.!2 REVERSE_DIRECTORY!GThis specifies the base directory or name entry to use when redirectingFthe reverse address mapping links (also called back translation links)"from the old to the new node name." oREVERSE_DIRECTORY rev-dir-nameCThe links under this directory are used to map NSAP values to theirFrespective node names. These directories are used only for the DECdnsdirectory service.FIf not specified, the default reverse directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.FFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!2 SYNONYM_DIRECTORY!GThis specifies the base directory or name entry to use when repdirecting;the synonym mapping link from the old to the new node name." SYNONYM_DIRECTORY syn-dir-nameCThe links under this directory are used to map Phase IV synonyms toEtheir respective node names. These directories are used only for theDECdns directory service.FIf not specified, the default synonym directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.FFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!q! ww 1 REPAIR!CRepair the synonym and reverse address mapping links for nodes in adirectory service." REPAIR [DECNET] NODE node-name) [ DIRECTORY_SERVICE dir-service ]* [ REVERSE_DIRECTORY rev-dir-name ]* [ SYNONYM_DIRECTORY syn-dir-name ]HThis is used when a node's synonym and reverse address mapping links areGaccidentally deleted or otherwise changed to that they no longer map toHthe correct node name. To determine whether or not a rnode's synonym andHreverse address mapping links are correct, use the SHOW command with the FULL keyword.!2 NODE!CThis specifies the name of the node whose links are to be repaired. NODE node-nameGThis argument is not used when repairing the Local Naming Database. Itis used only for DECdns.BThe node name must be the fully specified name for the node in the directory service. For example:, For DECdns: NODE MyCo:.Sales.MailHubBWildcards are allowed in the nodse name using an asterisk (*). Forexample:* For DECdns: NODE MyCo:.Sales.Mail*FThe wildcard character can come anywhere in the last part of the name.,Only a single wildcard character is allowed.HThe Phase IV database does not require or use synonym or reverse addressFmapping links. This command does not apply to this directory service.!2 DIRECTORY_SERVICE!GThis specifies the directory service that contains the node whose linksare to be repaired.! DIRECTORY_SEtRVICE dir-serviceThe service must be one of: DIRECTORY_SERVICE LOCAL DIRECTORY_SERVICE DECDNS@The Phase IV database does not require or use synonym or reverseEaddress mapping links. This command does not apply to this directoryservice.HIf not specified, the default service type is used. This default can be<displayed or changed using the SHOW or SET DEFAULT commands.!2 REVERSE_DIRECTORY!EThis specifies the base directory or name entry to use when repairingGth ue reverse address mapping links (also called back translation links)." REVERSE_DIRECTORY rev-dir-nameGThis argument is not used when repairing the Local Naming Database. Itis used only for DECdns.CThe links under this directory are used to map NSAP values to theirFrespective node names. These directories are used only for the DECdnsdirectory service.FIf not specified, the default reverse directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULvT commands.FFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!2 SYNONYM_DIRECTORY!EThis specifies the base directory or name entry to use when repairingthe synonym mapping link." SYNONYM_DIRECTORY syn-dir-nameGThis argument is not used when repairing the Local Naming Database. Itis used only for DECdns.CThe links under this directory are used to map Phase IV synonyms toEtheir respective node names. These directories are used only for theDECdwns directory service.FIf not specified, the default synonym directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.FFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!! ww 1 RESET!JReset the default values for optional parameters to their original values. RESET DEFAULT [ ALL ] [ DIRECTORY_SERVICE ] [ DISPLAY_MODE ] [ NSAP_FORMAT ] [ PHASEIV_xPREFIX ] [ REVERSE_DIRECTORY ] [ SYNONYM_DIRECTORY ]! 2 DEFAULT!EThis keywork is required. It indicates that default parameter valuesare being modified.BSee the RESET topic for a general description of the RESET DEFAULTcommand.!2 ALL!CThis resets the default values for all optional parameters to theiroriginal values. RESET DEFAULT ALL!2 DIRECTORY_SERVICE!@This resets the default directory service to its original value.# RESET yDEFAULT DIRECTORY_SERVICE!2 DISPLAY_MODE!;This resets the default display mode to its original value. RESET DEFAULT DISPLAY_MODE! 2 NSAP_FORMAT!AThis resets the default NSAP display style to its original value. RESET DEFAULT NSAP_FORMAT!2 PHASEIV_PREFIX!DThis resets the default Phase IV prefix value to its original value.HThis specifies the default AFI, IDI, and preDSP to use when constructing an NSAP from a Phase IV address. RESET DEFAULT PHASEIV_zPREFIXASee the PHASE_IV_PREFIXES topic for details about Phase IV prefixvalues.!2 REVERSE_DIRECTORY!CThis resets the default base directory or name entry to use for theDreverse address mapping links to the node name (also called the backEtranslation links) to its original value, for all directory services.# RESET DEFAULT REVERSE_DIRECTORYFFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!2 SYNONYM_DIRECTORY!GThis resets the default base dir{ectory or name entry to use for synonym@mapping links to its original value, for all directory services.# RESET DEFAULT SYNONYM_DIRECTORYFFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!! ww 1 SET!2Modify the default values for optional parameters. SET DEFAULT) [ DIRECTORY_SERVICE dir-service ]% [ DISPLAY_MODE display-mode ] [ NSAP_FORMAT format ]& [ PHASEIV_PREFIX addr-prefix ]* [ RE|VERSE_DIRECTORY rev-dir-name ]* [ SYNONYM_DIRECTORY syn-dir-name ]HThis provides a means to preset the values for commonly used parameters,Jsuch as the reverse address mapping directory name to use for a particulardirectory service.IThis is particularly useful when done in a DECNET_REGISTER initialization<command file (see "HELP USAGE INITIALIZATION_COMMAND_FILE").! 2 DEFAULT!EThis keywork is required. It indicates that default parameter valuesare being modified.GSe}e the SET topic for a general description of the SET DEFAULT command.!2 DIRECTORY_SERVICE!DThis specifies the directory service to use as the default, when the-command does not specify a directory service.! DIRECTORY_SERVICE dir-serviceThe service must be one of: DIRECTORY_SERVICE LOCAL DIRECTORY_SERVICE DECDNS DIRECTORY_SERVICE PHASEIVFIf other parameters are specified in the command, this also determinesDthe directory service that those additional defa~ult value parametersapply to. For example:I SET DEFAULT DIRECTORY_SERVICE DECdns REVERSE_DIR .DNA_BackTranslation!2 DISPLAY_MODE!CThis specifies the default display mode to use when the mode is notEexplicitly requested in the command. The following display modes are provided.1 DISPLAY_MODE NAMES Display only the names6 DISPLAY_MODE BRIEF Display names and addressesB DISPLAY_MODE FULL Display and error check all information For example:! SET DEFAULT DISPLAY_MODE FULLBSee the SHOW DISPLAY-MODE topic for more information on each mode.! 2 NSAP_FORMAT!HThis specifies the default NSAP display format to use when the format isGnot explicitly requested in the command. The following display formats are provided.( NSAP_FORMAT DNA Use DNA format( NSAP_FORMAT OSI Use OSI format For example: SET DEFAULT NSAP_FORMAT OSIDSee the SHOW NSAP_FORMAT topic for more information on these displayformats.!2 PHASEIV_PREFIX!HThis specifies the default AFI, IDI, and preDSP to use when constructingFan NSAP from a Phase IV address. This is used when a Phase IV addressHis specified in an address tower, and an explicit Phase IV prefix is not specified. PHASEIV_PREFIX addr-prefix For example:. SET DEFAULT PHASEIV_PREFIX 39:840:800AB738ASee the PHASE_IV_PREFIXES topic for details about Phase IV prefixvalues.!2 REVERSE_DIRECTORY!FThis specifies the default base directory or name entry to use for theDreverse address mapping links to the node name (also called the backtranslation links)." REVERSE_DIRECTORY rev-dir-nameCThe links under this directory are used to map NSAP values to theirFrespective node names. These directories are used only for the DECdnsdirectory service. For example:I SET DEFAULT DIRECTORY_SERVICE DECDNS REVERSE_DIR .DNA_BackTranslationFFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!2 SYNONYM_DIRECTORY!FThis specifies the default base directory or name entry to use for the&synonym mapping link to the node name." SYNONYM_DIRECTORY syn-dir-nameCThe links under this directory are used to map Phase IV synonyms toEtheir respective node names. These directories are used only for theDECdns directory service. For example:E SET DEFAULT DIRECTORY_SERVICE DECDNS SYNONYM_DIR .DNA_NodeSynonymFFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!! ww 1 SHOW!?Display the current default values for all optional parameters. SHOW DEFAULTDDisplay information from a node registration in a directory service. SHOW [DECNET] NODE node-id) [ DIRECTORY_SERVICE dir-service ] [ display-mode ]& [ PHASEIV_PREFIX addr-prefix ]* [ REVERSE_DIRECTORY rev-dir-name ]* [ SYNONYM_DIRECTORY syn-dir-name ] [ NSAP_FORMAT format ]% [ OUTPUT_FILE out-file-name ]JThe SHOW NODE command reads node registration information from a directoryJservice and displays it on the screen or writes it to a file. If the FULLIdisplay mode is used, this also verifies that all reverse address mapping3and synonym links are set up properly for the node.! 2 DEFAULT!DThis specifies that the current default parameter settings are to be displayed.DAll defaults are displayed. This command takes no other parameters.!2 NODE!;This specifies the identification of the nodes to be shown. NODE node-id&The node identification can be one of:C The fully specified name for the node in the directory service.& The Phase IV synonym for the node.2 One of the NET or NSAP addresses for the node.E The Phase IV address (and optional Phase IV prefix) for the node.-Wildcards are allowed in names and addresses.!3 Names!@The node to be shown can be specified using its full name or itsPhase IV synonym.EThe syntax of a fully specified name depends on the directory service8being used. Examples of fully specified names might be: For Local: NODE MailHub, For DECdns: NODE MyCo:.Sales.MailHub For Phase IV: NODE MLHUB?An example of a Phase IV synonym for any of the above might be: NODE MLHUBBWildcards are allowed in the node name using an asterisk (*). Forexample: For Local: NODE Mail** For DECdns: NODE MyCo:.Sales.Mail* For Phase IV: NODE ML*FThe wildcard character can come anywhere in the last part of the name.,Only a single wildcard character is allowed.! 3 Addresses!GThe node to be shown can be specified using one of its NETs (or NSAPs),or its Phase IV address.GAn NET is an NSAP address value with an N-Sel value of "00" (indicatingEthat it is independent of the type of transport service in use on theGnode). If you specify an NSAP instead of an NET, it is converted to anNET before it is used.9 DNA format: ::-::005 OSI format: +00Examples of NETs might be:4 DNA format: NODE 39:840:0001:AA-00-04-00-05-04:00, OSI format: NODE 39840+0001AA000400050400GIf the node has a Phase IV address, that can be used instead of an NET. Format: .' .+HThis is internally converted to an NET, using the Phase IV prefix value.GThe Phase IV prefix value can be specified with the Ph ase IV address orCthe PHASEIV_PREFIX parameter, or set using the SET DEFAULT command.(Examples of a Phase IV address might be:C NODE 1.5 !Uses the default Phase IV prefixC NODE 1.5+39:840 !Uses an explicit Phase IV prefixC NODE 1.5 PHASEIV_PREFIX 39:840 !Uses an explicit Phase IV prefixGWildcards are allowed in the NET or Phase IV address using an asterisk.DThe wildcard character must replace either the node id, or the localGarea and the node id. For an NET containing a wildcard, do not specifyan N-Sel value.9 39:840:0001:* (or 39840+0001*) Wildcard the node idH 39:840:* (or 39840+*) Wildcard the local area and node id9 1.* Wildcard the node idB *.* Wildcard the area and node id!2 DIRECTORY_SERVICE!IThis specifies the directory service that contains the node registration.! DIRECTORY_SERVICE dir-serviceThe service must be one of: DIRECTORY_SERVICE LOCAL DIRECTORY_SERVICE DECDNS DIRECTORY_SERVICE PHASEIVHIf not specified, the default service type is used. This default can be<displayed or changed using the SHOW or SET DEFAULT commands.!2 Display-Mode!BThe following display modes are provided, to display the indicated information. NAMESD - The fully specified name, as defined in the directory service. BRIEFD - The fully specified name, as defined in the directory service.H - The name of the link (if any) used to access the node information.8 - The Phase IV synonym name registered for the node.1 - The NSAP addresses registered for the node. FULL) - Same information as the BRIEF mode.< - The address tower information registered for the node.F - The link name used to map the synonym to the node name (if any).J - The link names used to map NSAP addresses to the node name (if any).EThe FULL mode also provides consistency checking, and prints messagesJdescribing any inconsistencies it finds, such as a missing synonym or NSAP9address link, or a link that points at an incorrect name.3If no mode is specified, the BRIEF mode is assumed.!2 PHASEIV_PREFIX!CThis specifies the AFI, IDI, and preDSP to use when constructing anGNET from a Phase IV address. This is used only when a Phase IV addressis specified for the node id. PHASEIV_PREFIX addr-prefixGAn alternate form is to add the Phase IV prefix to the Phase IV addressspecification. For example:+ NODE 1.5 PHASEIV_PREFIX 39:840:800AB738 NODE 1.5+39:840:800AB738Bwould both result in the following NET being used to represent theDECnet Phase IV address:- 39:840:800AB738-0001:AA-00-04-00-05-04:00HIf not specified, the default Phase IV prefix is used. This default can?be displayed or changed using the SHOW or SET DEFAULT commands.ISee the PHASE_IV_PREFIXES topic for details about Phase IV prefix values.!2 REVERSE_DIRECTORY!HThis specifies the base directory or name entry to use when checking andJdisplaying the reverse address mapping links to the node name (also calledthe back translation links)." REVERSE_DIRECTORY rev-dir-nameCThe links under this directory are used to map NSAP values to theirFrespective node names. These directories are used only for the DECdnsdirectory service.FIf not specified, the default reverse directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.FFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!2 SYNONYM_DIRECTORY!HThis specifies the base directory or name entry to use when checking and5displaying the synonym mapping link to the node name." SYNONYM_DIRECTORY syn-dir-nameCThe links under this directory are used to map Phase IV synonyms toEtheir respective node names. These directories are used only for theDECdns directory service.FIf not specified, the default synonym directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.FFor more information, please refer to the NAMES_AND_DIRECTORIES topic.! 2 NSAP_FORMAT!HThis specified the format to use when converting NSAP addresses to their text representation for display. NSAP_FORMAT DNA NSAP_FORMAT OSI.This causes the appropriate format to be used:? DNA format: ::-::; OSI format: +GIf not specified, the default NSAP format is used. This default can be<displayed or changed using the SHOW or SET DEFAULT commands.! 2 OUTPUT_FILE!BThis specifies the name of the file to receive the display output. OUTPUT_FILE out-file-nameFThis is useful if a lot of display output is to be generated for laterFexamination. If the specified file does not exist, it is created. IfAit already exists, the new information is appended to the current contents.;If not specified, all display output is sent to the screen.! wwhg 1 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_REGISTER when the execution is complete.CIf you do not specify the optional DCL command, you are placed in aFsubprocess and presented with the DCL prompt. When you log out of the/subprocess, control returns to DECNET_REGISTER.! wwhg 1 UPDATE!>Update a node's addressing information in a directory service." UPDATE [DECNET] NODE node-name) [ DIRECTORY_SERVICE dir-service ] [ ADDRESS addr-value ]& [ PHASEIV_PREFIX addr-prefix ]* [ REVERSE_DIRECTORY rev-dir-name ]HThis reads a node's addressing information directly from the node, usingEnetwork management, and modifies the node registration to contain thecorrect addresses.IIf an explicit node name is entered, the address to use to connect to theInode can also be explicitly entered. If an address is not specified, theHcurrently registered addresses for the node are tried. If none of these-result in a connection, an error is reported.IIf the node name contains a wildcard, an address cannot be specified. InIthis case, the currently registered addresses for each matching node nameJare tried. If none of these result in a connection for a particular node,#an error is reported for that node.!2 NODE!9This specifies the name of the new node to be registered. NODE node-name&The node identification can be one of:C The fully specified name for the node in the directory service.& The Phase IV synonym for the node.EThe syntax of a fully specified name depends on the directory service8being used. Examples of fully specified names might be: For Local: NODE MailHub, For DECdns: NODE MyCo:.Sales.MailHub For Phase IV: NODE MLHUB?An example of a Phase IV synonym for any of the above might be: NODE MLHUBBWildcards are allowed in the node name using an asterisk (*). Forexample: For Local: NODE Mail** For DECdns: NODE MyCo:.Sales.Mail* For Phase IV: NODE ML*FThe wildcard character can come anywhere in the last part of the name.,Only a single wildcard character is allowed.!2 DIRECTORY_SERVICE!BThis specifies the directory service the node is to be updated in.! DIRECTORY_SERVICE dir-serviceThe service must be one of: DIRECTORY_SERVICE LOCAL DIRECTORY_SERVICE DECDNS DIRECTORY_SERVICE PHASEIVHIf not specified, the default service type is used. This default can be<displayed or changed using the SHOW or SET DEFAULT commands.! 2 ADDRESS!GThis specifies an address to use when establishing a network managementCconnection to the node. This parameter can be specified only if an;explicit node name is entered, with no wildcard characters.DOnce the connection is established, the node's tower set is obtained2and is used to update the directory service entry. The address value can be one of:+ One of the node's NET or NSAP addresses The node's Phase IV address The keyword "LOCAL" (or "0")GAn NET is an NSAP address value with an N-Sel value of "00" (indicatingEthat it is independent of the type of transport service in use on theGnode). If you specify an NSAP instead of an NET, it is converted to anNET before it is used.9 DNA format: ::-::005 OSI format: +00Examples of NETs might be:7 DNA format: ADDRESS 39:840:0001:AA-00-04-00-05-04:00/ OSI format: ADDRESS 39840+0001AA000400050400GIf the node has a Phase IV address, that can be used instead of an NET. Format: .' .+HThis is internally converted to an NET, using the Phase IV prefix value.GThe Phase IV prefix value can be specified with the Phase IV address orCthe PHASEIV_PREFIX parameter, or set using the SET DEFAULT command.(Examples of a Phase IV address might be:F ADDRESS 1.5 !Uses the default Phase IV prefixF ADDRESS 1.5+39:840 !Uses an explicit Phase IV prefixF ADDRESS 1.5 PHASEIV_PREFIX 39:840 !Uses an explicit Phase IV prefixGIf the node whose directory service entry is to be updated is the localGnode, use "LOCAL" (or "0"). This will force the use of a local network$management connection. For example: ADDRESS LOCAL ADDRESS 0EIf not specified, the currently registered addresses for the node areFtried. If none of these result in a connection, an error is reported.!2 PHASEIV_PREFIX!CThis specifies the AFI, IDI, and preDSP to use when constructing anCNSAP from a Phase IV address. This is used when a Phase IV address&is specified in the ADDRESS parameter. PHASEIV_PREFIX addr-prefix For example:. ADDRESS 1.5 PHASEIV_PREFIX 39:840:800AB738Ewould result in the following NSAP being used to represent the DECnetPhase IV address:- 39:840:800AB738-0001:AA-00-04-00-05-04:20-An alternate way of expressing this would be: ADDRESS 1.5+39:840:800AB738HIf not specified, the default Phase IV prefix is used. This default can?be displayed or changed using the SHOW or SET DEFAULT commands.ISee the PHASE_IV_PREFIXES topic for details about Phase IV prefix values.!2 REVERSE_DIRECTORY!DThis specifies the base directory or name entry to use when creatingCthe reverse address mapping links to the node name (also called theback translation links)." REVERSE_DIRECTORY rev-dir-nameCThe links under this directory are used to map NSAP values to theirFrespective node names. These directories are used only for the DECdnsdirectory service.FIf not specified, the default reverse directory is used. This defaultCcan be displayed or changed using the SHOW or SET DEFAULT commands.FFor more information, please refer to the NAMES_AND_DIRECTORIES topic.!! wwhg 1 Address_Towers!@Address towers are used in the REGISTER, MODIFY, ADD, and REMOVEFcommands, by specifying the TOWERS parameter. The format for a TOWERS parameter is: TOWERS {tower, tower, ...}-Each address tower in the set has the format: transport/addressEFields can be omitted from left to right, and assume a default value.!!2 Transport_Field!=This field indicates the Transport type. This can be either:# TP4 - OSI Transport Class 47 NSP - DECnet Phase IV Network Services ProtocolGIf TP4 is specified, it can be followed by an optional T-Sel value as aHseries of hexadecimal digits after an equals sign. If an explicit T-SelDvalue is not specified, the DECnet default of "TP4=DEC0" is assumed. For example:0 TP4=AB12 - The T-Sel value is set to "AB12"I TP4=AB1 - The T-Sel value is "AB10" (number of digits must be even)7 TP4 - The T-Sel value is assumed to be "DEC0"IIf a transport type is not specified, the default depends on the address.E NSP is used if the address is specified using Phase IV format, or+ is an NSAP with an N-Sel value of "20".C TP4 is used if the address is an NSAP with an N-Sel value other than "20".!2 Address_Field!CThis field indicates the node address. This can be specified using&either Phase IV format or NSAP format.# Phase IV format: ., .+B DNA NSAP format: ::-::> OSI NSAP format: +;See PHASE_IV_ADDRESSES and NSAP_ADDRESSES for more details.! 2 Examples!HAssuming that the Phase IV address prefix value is "49 ::", some examplesof address towers are:3 Abbreviation Fully Specified3 ------------ ---------------> 1.5 NSP/49::01:AA0004000504:20> 1.5 NSP/49::01:AA0004000504:20A 39:840:01:AA0004000504:20 NSP/39:840:01:AA0004000504:20F 39:840:01:AA0004000504:21 TP4=DEC0/39:840:01:AA0004000504:21F TP4/39:840:01:AA0004000504:21 TP4=DEC0/39:840:01:AA0004000504:21HExamples of address towers using normal default values for both a DECnet.Phase IV node and a DECnet-Plus node might be: TOWERS={1.5}E TOWERS={2.54, 39:840:01:AA0004000504:20, 39:840:01:AA0004000504:21}! ww, 1 NSAP_Addresses!:NSAP addresses are used when registering or modifying nodeBinformation. They can also be used when specifying nodes to show,export, or deregister.!The format for an NSAP is either:@ DNA format - ::-::< OSI format - +Where:9 - The AFI (Authority and Format Identifier)3 - The IDI (Initial Domain Identifier)D - The prefix portion of the DSP (Domain Specific Part)1 - The local area portion of the DSP. - The node id portion of the DSP? - The N-Sel (Network Selector) portion of the DSPEach address field contains: AFI 2 decimal digitsD IDI some number of decimal digits, determined by the AFI@ PreDSP some number of hex digits, determined by the AFI$ Local area 4 hexadecimal digits% Node id 12 hexadecimal digits$ N-Sel 2 hexadecimal digitsDWhen using DNA format NSAPs, the preDSP, local area, and node id canEcontain embedded hyphens ("-") to improve readability. Also, leading?zeros in the local area and node id fields can be dropped. For4example, the following two addresses are equivalent.$ 39:840:0001:AA-00-04-00-05-04:20 39:840:1:AA0004000504:21BWhen using OSI format NSAPs, embedded hyphens are not allowed, and;leading zeros cannot be dropped in any field. For example: 39840+0001AA000400050421=An N-Sel of "20" specifies the use of the DECnet Phase IV NSP>transport. Any other N-Sel value (such as "21") indicates the0use of the OSI Transport Class 4 protocol (TP4).GIf specified for the NODE parameter, wildcards (indicated by asterisks)Dcan generally be used to indicate multiple nodes, for example in theGSHOW, DEREGISTER, and EXPORT commands. Either the node id or the localCarea plus node id can be wildcarded. When using a wildcard, do notspecify the N-Sel, For example:= 39:840:56A1-0001:* (all nodes in area 39:840:8056A1-0001)G 39:840:56A1* (all nodes in all local areas under 39:840:56A1)! ww, 1 Phase_IV_Addresses!>Phase IV addresses are used when registering or modifying nodeBinformation. They can also be used when specifying nodes to show,export, or deregister.,The format for a Phase IV address is either: . .+Where:* - The area number, from 1 to 638 - The node id within the area, from 1 to 1023) - The optional Phase IV prefix For example: 1.5 1.5+39:840:DWhen a Phase IV format address is specified, it is combined with theDPhase IV prefix value to create an NSAP. This Phase IV prefix value8consists of the AFI, IDI, and preDSP fields of the NSAP.BThe Phase IV prefix can be specified with the Phase IV address, as?shown above. It can also be specified using the PHASEIV_PREFIXGparameter. The advantage of using the PHASEIV_PREFIX parameter is that>the value is applied to all Phase IV addresses in the command.HIf not specified using either of the above methods, the default Phase IVHprefix is used. This default can be displayed or changed using the SHOWor SET DEFAULT commands.GIf specified for the NODE parameter, wildcards (indicated by asterisks)Jcan generally be used to indicate multiple nodes, for example in the SHOW,JDEREGISTER, and EXPORT commands. Either the node id or the area plus node#id can be wildcarded. For example:! 1.* (all nodes in area 1)$ *.* (all nodes in all areas)! ww, 1 Phase_IV_Prefixes!GA Phase IV prefix is used to convert a Phase IV address to an NSAP. ItGconsists of the AFI, IDI, and preDSP fields of the NSAP. The format is either of:& DNA format - ::% OSI format - +Where:9 - The AFI (Authority and Format Identifier)3 - The IDI (Initial Domain Identifier)D - The prefix portion of the DSP (Domain Specific Part)Each address field contains: AFI 2 decimal digitsD IDI some number of decimal digits, determined by the AFI@ PreDSP some number of hex digits, determined by the AFIEA Phase IV prefix can be specified for an individual Phase IV address5by adding it to the end of the address. For example: TOWER {1.5+39:840:}BA Phase IV prefix can be specified for all Phase IV addresses in a<command by using the PHASEIV_PREFIX parameter. For example:+ TOWER {1.5, 1.6} PHASEIV_PREFIX 39:840:HIf not specified using either of the above methods, the default Phase IVHprefix is used. This default can be displayed or changed using the SHOWor SET DEFAULT commands.FThe local area and node id values are built from the Phase IV address,Dand the N-Sel value is generally "20" (for NSP), unless the Phase IVFprefix is being applied to a tower that specifies the use of TP4. Forexample:8 TOWERS {1.5, TP4/1.6} PHASEIV_PREFIX 39:840:800AB738Fwould result in the following NSAPs being used to represent the DECnetPhase IV addresses:- 39:840:800AB738-0001:AA-00-04-00-05-04:20- 39:840:800AB738-0001:AA-00-04-00-06-08:21! ww, 1 Names_and_Directories!BNode names are used to maintain node addressing information in theBdirectory service, allowing addressing information to be kept in aglobal repository.HFor those directory services that support hierarchical naming, names areCgenerally collected into groups using directories. Three types ofDdirectories are used for maintaining node information in a directoryservice. These are:I Node name directories, con taining node names that hold node informationE Reverse address mapping directories, used to map addresses to namesC Synonym mapping directory, used to map Phase IV synonyms to names:The names and directories are described in the sub-topics.! 2 Node_Names!FNode names contain addressing data that is used when an application onCone node needs to connect to an application on another named node. 8These names must be unique within the directory service.FSome directory services suppor t hierarchical naming. The names at theAvarious levels of the hierarchy, except for the lowest level, areEcommonly referred to as "directories". The names at the lowest levelAidentify the specific node within that part of the hierarchy, and?contain the node's addressing information. For these directoryAservices, it is the entire hierarchical name that must be unique.!!3 DECdns!EThis is a global directory service, where names are assigned within aEnaming hierarchy. The entire name, including all of its hierarchicalFlevels, makes up the "full name". One possible format for a full nameis: :...Where:G : is the name of the namespace for this naming hierarchy.C For example, this could represent the organization.G . is some directory name used to break the namespace downE into smaller, more manageable segments. For example,G this could represent an organization, an organizationalF unit, or a location within an organization. There can9 be as many levels of directory as needed.6 . is the terminating name for some node.FThe actual name structure can be defined to suit the name usage of theGorganization. If the above structure is used, an example of a completefull name might be: MYCO:.TOPEKA.MYNODE!!3 Local!DThe Local Naming Database uses flat naming, rather than hierarchical Fnaming. Names can consist of any text string. Because long names areEallowed, up to 100 characters for any name, a naming hierarchy can be:simulated by using common name prefixes for related names.FThe Local Naming Database is private to a particular node or cluster. HAs such, it must be manually kept up to date on all nodes if they are toHshare the same set of names. This can be done by exporting the contentsEof a master copy of the Local Naming Database to a text file, copyingEthe text file to other nodes as required, and importing the text file2into the Local Naming Database for each such node.4An example of a Local Naming Database name might be: TOPEKA.MYNODE! 3 Phase_IV!@The Phase IV Database uses flat naming, rather than hierarchicalBnaming. Names can consist of up to 6 letters (A to Z) and decimal*digits (0 to 9), with at least one letter.EThe Phase IV Database is private to a particular node or cluster. AsEsuch, it must be manually kept up to dat e on all nodes if they are toHshare the same set of names. This can be done by exporting the contentsEof a master copy of the Phase IV Database to a text file, copying theFtext file to other nodes as required, and importing the text file into)the Phase IV Database for each such node.0An example of a Phase IV Database name might be: MYNODE@The Phase IV Database is supported primarily to allow the simpleFmigration from DECnet Phase IV to DECnet-Plus and some other directoryservice.!2 Reverse_Address_Mapping!CReverse address mapping allows a node name to be determined from an#address (specifically from an NET).HFor directory services that support hierarchical naming, this is done byGsetting up directories and links within those directories, based on theINETs of the nodes in the network. Each link then points to the node name"associated with the indicated NET.!!3 DECdns!DSoft link names are used to map NETs to their respective node names.BThe default value for the reverse address mapping directory in theDECdns directory service is: .DNA_BackTranslationHIf not specified using either of the above methods, the default Phase IVHprefix is used. This default can be displayed or changed using the SHOWor SET DEFAULT commands.@The directory name can be changed for a single command using theDREVERSE_MAPPING parameter, or for all commands using the SET DEFAULTcommand.FThere are two more levels of directory under this top level directory,>followed by the actual soft link name. The name structure is:2 .DNA_BackTranslation...Where:C is the value of the binary NET up to the local area field.G is the value of the local area field in the binary NET.D is the value of the node id field in the binary NET.CFor example, for an NET of "39:840:00-01:AA-00-04-00-05-04:20", the(fully specified soft link name would be:5 .DNA_BackTranslation.%X39840F.%X0001.%XAA0004000504HThe "F" in the second level directory is a padding value that is presentEin the binary form of the NSAP value, though it is not visible in theuser representation.!!3 Local!FThe Local Naming Database does not make use of reverse address mappingGfor mapping addresses to names. Instead, addresses are treated as keys'within the indexed Local Database file.! 3 Phase_IV!FThe Phase IV Database does not make use of reverse addre ss mapping forCmapping addresses to names. Instead, addresses are treated as keys*within the indexed Phase IV Database file.!2 Synonym_Mapping!CSynonym mapping allows a node name to be determined from a Phase IVsynonym assigned to that node.HFor directory services that support hierarchical naming, this is done byGsetting up directories and links within those directories, based on theEsynonyms assigned to the nodes in the network. Each link then points7to the node name associated with the indicated synonym.!!3 DECdns!ASoft link names are used to map synonyms to their respective nodenames.AThe default value for the synonym mapping directory in the DECdnsdirectory service is: .DNA_NodeSynonym@The directory name can be changed for a single command using theDREVERSE_MAPPING parameter, or for all commands using the SET DEFAULTcommand.GThis directory contains the actual soft link names. The name structureis: .DNA_NodeSynonym.Where:- is the Phase IV synonym name.HFor example, for the synonym "MYSYN", the fully specified soft link name would be: .DNA_NodeSynonym.MYSYN!!3 Local!BThe Local Naming Database does not make use of synonym mapping forCmapping Phase IV synonyms to names. Instead, the Phase IV synonyms;are treated as keys within the indexed Local Database file.! 3 Phase_IV!FThe Phase IV Database does not make use of synonym mapping for mappingGPhase IV synonyms to names. This is because Phase IV synonym names are0the only names allowed in the Phase IV Database.! ww  1 Export_File!CAn export file is created using the EXPORT command. This is a textFfile containing node registration information read from some directoryservice.AThis file can be used as input to the IMPORT command to move nodeCinformation from one directory service to another, or to verify theEinformation in one or more directory services. It can also be editedDto change any information (such as the NSAP IDP used by the network)>and used to bulk modify the contents of the directory service.)The file contains the following sections. # # # # :# # DThe directory service and node registration information sections areGrepeated as often as necessary to ensure that the appropriate directoryDservice information is associated with the correct node registration information.!2 Type_and_Version!IThis section contains the following information. Lines beginning with anDequals sign (=) contain control information (the equals sign must beHin the first character position, or it is treated as the first characterof a node name). =Type DECnet Node =Version 1JThese lines specify the file contents and version. The values shown above)are the only currently recognized values.!2 Directory_Service_Information!IThis section contains the following information. Lines beginning with anGequals sign (=) contain control information (the equals sign must be inHthe first character position, or it is treated as the first character of a node name)./ =All Address Prefix ???6 =DECdns Name Template ???:.???.*0 =DECdns Synonym Directory .???0 =DECdns Reverse Address Directory .???0 =LocalFile Name Template ???*- =PhaseIV Name Template *IThe information specified in this section provides default values for useDwhen importing into the indicated directory service ("All" indicates5information that is used for all directory services).DLines from this section can be repeated further down in the file, toDchange the supplied informatio n. For example, this is useful when aDfile contains node information that is to be registered into several6directories (specified using the Name Template value).GInitially, the value for each piece of information is set to "unknown",Gby writing question marks (???) to the file. If the EXPORT command canHdetermine an appropriate value for any of these, it places that value inFthe file instead. This is possible only for the directory service youare exporting from.JWhen the file is rea d by the IMPORT command, only those lines intended forGthe target directory service are examined. All others are ignored, andHcan contain invalid values without causing an error. Also, each line inJthis section has an equivalent IMPORT command parameter. If the parameterHis specified in the IMPORT command, then the value contained in the fileGfor that parameter is ignored, and can contain an invalid value withoutcausing an error. BSee the IMPORT command for an explanation of each parameter value.!2 Node_Registration_Information!JThis section contains the node registration information. These lines mustHnot begin with an equals sign (=) in the first character position. If aGnode uses an equals sign as the first character in its name, indent thename by at least one space.*The format for a node information line is:< name synonym {TOWER=tower, TOWER=tower, ..., TOWER=tower}Where:C name The terminating part of the name for the node. This isF generally the part of the name that is the same regardlessD of the directory service. For example, "MailHub" is the/ terminating name for the following:# Local: MailHub/ DECdns: MyCo:.Sales.MailHubF When importing into the Phase IV Database, this is ignoredE and the synonym field used used, if a synonym is defined.E If a synonym is not defined, and the name is not Phase IV) compatible, an error results.I synonym The Phase IV synonym for the node, if any. This is optional.E tower A tower value for the node. The format for an individualF tower is the same as it is in a TOWERS parameter. See theB ADDRESS_TOWERS topic for a description of this format.G All directory services except the Phase IV database supportF multiple towers. If importing into the Phase IV Database,8 the first Phase IV compatible tower is used.C The braces surrounding the list of towers are required. For example:F MailHub MLHUB {Tower=12.2, Tower=37:840:0001:08-00-2B-0D-E9-B1:21}ww