% Librarian A09-300](Dv  56eDEREGISTER_NODE_INFORMATIONmEXPORT_NODE_INFORMATIONuIMPORT_NODE_INFORMATION  MAIN_MENUMANAGE_DIRECTORIESI|REGISTER_NODE_INFORMATIONQREGISTER_NODE_TOWERS^ RENAME_NODEb REPAIR_NODE}jSET_PREFERENCES@6SHOW_NODE_INFORMATIONUUPDATE_NODE_INFORMATION Dt 1 MAIN_MENU!DThe DECNET_REGISTER utility provides network managers with functionsCto help manage node names in the directory service or services usedwithin the network.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 re gistration 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 serviceE - Repair the synonym and address mapping links for registered nodes. - Deregister a node from a directory service%The supported directory services are:7 Local Naming Database DECdns Phase IV DatabaseBTo obtain help on how to answer the questions in any form, enter a5question mark (?) to any of the prompts in that form.! ! Under MAIN_MENU 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 isFcomplete. If not, it brings the main menu up on the screen and startsaccepting function requests.!! ! Under MAIN_MENU 2 Termination!@To exit, press the Ctrl/Z key combination when in the main menu.FIf a command was specified on the invocation command line, the utility7exits immediately after the command has been processed.! ! Under MAIN_MENU2 Initialization_Command_File!BOn startup, the DECNET_REGISTER utility always attempts to execute?an initialization command file if one is present. This is mostCuseful for pre-setting the values in the preferences form to valuesother than the normal defaults.! /! Under MAIN_MENU / Initialization_Command_File 3 File_name!ADECNET_REGISTER checks for an initialization file using a defaultname of:! SYS$LOGIN:DECNET_REGISTER.INIEIf this file is found, 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.! /! Under MAIN_MENU / Initialization_Command_File 3 Commands!@The most useful commands to place in an initialization file are:+ SET DEFAULT DIRECTORY_SERVICE dir-service> This sets the default directory service, where dir-service, can be either LOCAL, DECDNS, or PHASEIV.' SET DEFAULT DISPLAY_MODE display-mode> This sets the default show information display mode, where5 display-mode can be either BRIEF, FULL, or NAMES.  SET DEFAULT NSAP_FORMAT format; This sets the default NSAP display format, where format can be either DNA or OSI.( SET DEFAULT PHASEIV_PREFIX addr-prefix: This sets the default AFI, IDI, and preDSP to use when: constructing an NSAP from a Phase IV address. See the7 MAIN_MENU PHASE_IV_PREFIXES topic for details about Phase IV prefix values., SET DEFAULT REVERSE_DIRECTORY rev-dir-name9 This sets the default base directory or name entry to9 use for the reverse address mapping links to the node; name (also called the back translation links). See the; MAIN_MENU NAMES_AND_DIRECTORIES REVERSE_ADDRESS_MAPPING topic for more information., SET DEFAULT SYNONYM_DIRECTORY syn-dir-name9 This sets the default base directory or name entry to; use for the synonym mapping link to the node name. See7 the MAIN_MENU NAMES_AND_DIRECTORIES SYNONYM_MAPPING topic for more information.AFor more information on using commands, invoke DECNET_REGISTER inAcommand line interface mode, and enter the HELP command. See theCMAIN_MENU iNTERFACE_MODES topic for information on entering command line mode.! ! Under MAIN_MENU2 Interface_Modes!?After DECNET_REGISTER is invoked, and after it has executed the<initialization command file (if any), it enters either formsmode or command line mode.DForms mode is used if the utility is invoked from a video terminal. BCommand line mode is used if the utility is in voked from a command#file or from a hardcopy terminal. EThe DECNET_REGISTER utility can be forced to always run in forms mode=or command line mode by using one of the logical definitions:? $ DEFINE DECNET_REGISTER_FORMS 1 !Force the use of formsG $ DEFINE DECNET_REGISTER_COMMANDS 1 !Force the use of command linesAIf either of these is defined, DECNET_REGISTER uses the indicated0interface mode, regardless of how it is invoked.FThe DECNET_REGISTER utility can also be forced to run in forms mode or@command line mode by supplying one of the following arguments onthe invocation command line:: $ NETREG /F !Force the use of formsB $ NETREG /C !Force the use of command linesGTo 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.! ! Under MAIN_MENU2 Entering_Information!&When entering in formation to a prompt:J - If entering a keyword, such as the directory service type, the keywordI can be entered using either upper or lower case, and can generally be9 abbreviated to three, or sometimes fewer, characters.H - If entering user-supplied information, such as node names, enter theJ string with no abbreviations. Some information, such as node names in8 particular, must be entered in the appropriate case.F - Entering a question mark (?) to any prompt in a form provides helpG information on that form, with sub-topics for the various fields in that form.! ! Under MAIN_MENU2 NSAP_Addresses!HNSAP addresses are used when registering or modifying node information. ?They can also be used when specifying nodes to show, export, or deregister.)The format for an NSAP address 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 for mat 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 used when indicating nodes to show, export, or deregister, wildcardsH(indicated by asterisks) can be used to indicate multiple nodes. EitherIthe node id or the local area plus node id can be wildcarded. When using2a wildcard, do not specify 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)! ! Under MAIN_MENU2 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 value@consists of the AFI, IDI, and preDSP fields of the NSAP. If theEPhase IV prefix is not specified with the Phase IV address, the value$set in the preferences form is used.HIf a Phase IV address is used when indicating the nodes to show, export,@or deregister, wildcards (indicated by asterisks) can be used toBindicate multiple nodes. 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)! ! Under MAIN_MENU2 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: 1.5+39:840:EA default Phase IV prefix can be specified for all Phase IV addressesusing the preferences form.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 IVEprefix is being applied to an address tower that speci"fies the use ofTP4.! ! Under MAIN_MENU2 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, contain #ing 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.! )! Under MAIN_MENU / Names_and_Directories 3 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 se $rvice.FSome directory services support 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.! 6! Under MAIN_MENU / Names_and_Directories / Node_Names! 6! Under MAIN_MENU %/ Names_and_Directories / Node_Names4 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:F : is the name of the namespace for this naming hierarchy.B For example, this could represent the organization.F . is some directory name used & to break the namespace downD into smaller, more manageable segments. For example,F this could represent an organization, an organizationalE unit, or a location within an organization. There can8 be as many levels of directory as needed.5 . is the terminating name for some node.BThe actual name structure can be defined to suit the name usage ofBthe organization. If the above structure is used, an example of acomplete' full name might be: MYCO:.TOPEKA.MYNODE! 6! Under MAIN_MENU / Names_and_Directories / Node_Names! 6! Under MAIN_MENU / Names_and_Directories / Node_Names4 Local!DThe Local Naming Database uses flat naming, rather than hierarchicalFnaming. 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 partic (ular node or cluster. EAs such, it must be manually kept up to date on all nodes if they areBto share the same set of names. This can be done by exporting theFcontents of a master copy of the Local Naming Database to a text file,Ccopying the text file to other nodes as required, and importing the<text file into the Local Naming Database for each such node.4An example of a Local Naming Database name might be: TOPEKA.MYNODE! 6! Under MAIN_MENU / Names_and_Directories / Node_Names 4 )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 date on all nodes if they are to?share the same set of names. This can be done by exporting theBcontents of a master copy of the Phase IV Database to a text file,Ccopying the text file to other nod*es as required, and importing the8text 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.! )! Under MAIN_MENU / Names_and_Directories3 Reverse_Address_Mapping!CReverse address mapping allows a node name to be determined from an#address (specifically from an NET).EFor dire +ctory services that support hierarchical naming, this is doneFby setting up directories and links within those directories, based onCthe NETs of the nodes in the network. Each link then points to the,node name associated with the indicated NET.! C! Under MAIN_MENU / Names_and_Directories / Reverse_Address_Mapping! C! Under MAIN_MENU / Names_and_Directories / Reverse_Address_Mapping4 DECdns!DSoft link names are used to map NETs to their respective node names.EThe normal default v,alue for the reverse address mapping directory in the DECdns directory service is: .DNA_BackTranslationEThe default directory name can be changed using the preferences form.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:A is the value of the binary NET up to the local area field.E is the val-ue of the local area field in the binary NET.B 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 is:5 .DNA_BackTranslation.%X39840F.%X0001.%XAA0004000504@The "F" in the second level directory is a padding value that is>present in the binary form of the NSAP value, though it is not#visible in the user representation.! C! Under MAIN_MENU / Names_and_Directories / Reve.rse_Address_Mapping! C! Under MAIN_MENU / Names_and_Directories / Reverse_Address_Mapping4 Local!FThe Local Naming Database does not make use of reverse address mappingBfor mapping addresses to names. Instead, addresses are treated as,keys within the indexed Local Database file.! C! Under MAIN_MENU / Names_and_Directories / Reverse_Address_Mapping 4 Phase_IV!BThe Phase IV Database does not make use of reverse address mappingBfor mapping addresses to names. Instead, addresses /are treated as/keys within the indexed Phase IV Database file.! )! Under MAIN_MENU / Names_and_Directories3 Synonym_Mapping!CSynonym mapping allows a node name to be determined from a Phase IVsynonym assigned to that node.EFor directory services that support hierarchical naming, this is doneFby setting up directories and links within those directories, based onBthe synonyms assigned to the nodes in the network. Each link then>points to the node name associated with the indicate0d synonym.! ;! Under MAIN_MENU / Names_and_Directories / Synonym_Mapping! ;! Under MAIN_MENU / Names_and_Directories / Synonym_Mapping4 DECdns!ASoft link names are used to map synonyms to their respective nodenames.AThe normal default value for the synonym mapping directory in theDECdns directory service is: .DNA_NodeSynonymEThe default directory name can be changed using the preferences form.=This directory contains the actual soft link names. The name structure 1is: .DNA_NodeSynonym.Where:+ is the Phase IV synonym name.CFor example, for the synonym "MYSYN", the fully specified soft linkname is: .DNA_NodeSynonym.MYSYN! ;! Under MAIN_MENU / Names_and_Directories / Synonym_Mapping! ;! Under MAIN_MENU / Names_and_Directories / Synonym_Mapping4 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 k2eys within the indexed Local Database file.! ;! Under MAIN_MENU / Names_and_Directories / Synonym_Mapping 4 Phase_IV!>The Phase IV Database does not make use of synonym mapping for=mapping Phase IV synonyms to names. This is because Phase IVBsynonym names are the only names allowed in the Phase IV Database.! ! Under MAIN_MENU 2 Export_File!DAn export file is created using the export function. This is a textFfile containing node registration information read from some directo3ryservice.BThis file can be used as input to the import function 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.! ! Under MAIN_MENU / Export_File3 Type_and_Version!FThis section contains the following informat5ion. Lines beginning withGan equals 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 1DThese lines specify the file contents and version. The values shown/above are the only currently recognized values.! ! Under MAIN_MENU / Export_File3 Directory_Service_Information!FThis section contains the following information. Lines beginning withGan e6quals sign (=) contain control information (the equals sign must beHin the first character position, or it is treated as the first characterof a node name)./ =All Address Prefix ???0 =LocalFile Name Template ???*6 =DECdns Name Template ???:.???.*0 =DECdns Synonym Directory .???0 =DECdns Reverse Address Directory .???- =PhaseIV Name Template *EThe information specified in t 7his section provides default values forHuse when 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 information. 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 "un 8known",Hby writing question marks (???) to the file. If the export function 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.GWhen the file is read by the import function, only those lines intendedGfor the target directory service are examined. All others are ignored,Dand can contain invalid values without causing an error. Also, eachFline in this section has an equiva 9lent import function form field. IfGa value is specified in field, then the value contained in the file forGthat field is ignored, and can contain an invalid value without causing an error. GEnter a question mark (?) to the import form for an explanation of each field value.! ! Under MAIN_MENU / Export_File3 Node_Registration_Information!EThis section contains the node registration information. These linesHmust not begin with an equals sign (=) in the first character positi:on. HIf a node uses an equals sign as the first character in its name, indentthe name by at least one space.*The format for a node information line is:< name synonym {TOWER=tower, TOWER=tower, ..., TOWER=tower}Where:B name The terminating part of the name for the node. This isE generally the part of the name that is the same regardlessC of the directory service. For example, "MailHub" is the. terminating name for the following:# ; Local: MailHub/ DECdns: MyCo:.Sales.MailHubE When importing into the Phase IV Database, this is ignoredD and the synonym field used used, if a synonym is defined.D If a synonym is not defined, and the name is not Phase IV( compatible, an error results.H synonym The Phase IV synonym for the node, if any. This is optional.E tower A tower value for the node. Each address tower in the set has the for <mat: transport/addressD Fields can be omitted from left to right. Omitted fieldsF assume a default value. The format for an individual tower3 is given in the sub-topics listed below.F All directory services except the Phase IV database supportE multiple towers. If importing into the Phase IV Database,7 the first Phase IV compatible tower is used.B The braces surrounding the list of towers are requi=red. For example:F MailHub MLHUB {Tower=12.2, Tower=37:840:0001:08-00-2B-0D-E9-B1:21}! ! ?! Under MAIN_MENU / Export_File / Node_Registration_Information4 Transport_Tower_Field!=This field indicates the Transport type. This can be either:# TP4 - OSI Transport Class 47 NSP - DECnet Phase IV Network Services ProtocolEIf TP4 is specified, it can be followed by an optional T-Sel value asDa series of hexadecimal digits after an equals sign. If an explicitA>T-Sel value is not specified, the DECnet default of "TP4=DEC0" isassumed. For example:* TP4=AB12 - The T-Sel is set to "AB12"C TP4=AB1 - The T-Sel is "AB10" (number of digits must be even)1 TP4 - The T-Sel is assumed to be "DEC0"@If a transport type is not specified, the default depends on theaddress.B 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 a?n N-Sel value other than "20".!! ?! Under MAIN_MENU / Export_File / Node_Registration_Information4 Address_Tower_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_AD@DRESSES for more details.! ?! Under MAIN_MENU / Export_File / Node_Registration_Information4 Example_Towers!?Assuming that the Phase IV address prefix value is "49::", someexamples of address towers are: Abbreviation: 1.5. Fully Specified: NSP/49::01:AA0004000504:20- Abbreviation: 39:840:01:AA0004000504:201 Fully Specified: NSP/39:840:01:AA0004000504:20- Abbreviation: 39:840:01:AA0004000504:216 Fully Specified: TP4=DEC0/39:840:01:AA0004000504:211A Abbreviation: TP4/39:840:01:AA0004000504:216 Fully Specified: TP4=DEC0/39:840:01:AA0004000504:21AExamples of address towers using normal default values for both a5DECnet Phase IV node and a DECnet-Plus node might be: TOWERS={1.5}* TOWERS={2.54, 39:840:01:AA0004000504:21}! wwTu1 SHOW_NODE_INFORMATION!AThis function displays information about a node registration in adirectory service.!2 Directory_Service!AThis field specifies the directoryB service that contains the node6registration to be shown. The service must be one of: LOCAL DECDNS PHASEIVCThe service type can be abbreviated, as long as the abbreviation isunique.!2 Node_Name_or_Address!AThis field specifies the identification of the nodes to be shown.&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 tChe 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: MailHub' For DECdns: MyCo:.Sales.MailHub For Phase IV: MLHUB?An example of a Phase IV synonym fDor any of the above might be: MLHUBBWildcards are allowed in the node name using an asterisk (*). Forexample: For Local: Mail*% For DECdns: MyCo:.Sales.Mail* For Phase IV: 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 EN-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:/ DNA format: 39:840:0001:AA-00-04-00-05-04:00' OSI format: 39840+0001AA000400050400GIf the node has a Phase IV address, that can be used insteFad of an NET. Format: .' .+HThis is internally converted to an NET, using the Phase IV prefix value.EThe Phase IV prefix value can be specified with the Phase IV address,/or set as a default using the preferences form.(Examples of a Phase IV address might be:E 1.5 Uses the default Phase IV prefixE 1.5+39:840 Uses an explicit Phase IV prefixGWildcards are allowed inG 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 Display_Format!DTh He following display formats are provided, to display the indicatedAinformation. The format names can be abbreviated, as long as theabbreviation is unique. 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 I. FULL+ - Same information as the BRIEF format.< - 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).FThe FULL display format also provides consistency checking, and printsCmessages describing any inconsistencies it finds, such as a missingIsynonym or NSAP address link, or a link that points at an incorrect name.! 2 Output_FilJe!BThis specifies the name of the file to receive the display output.FThis 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.! wwTu1 REGISTER_NODE_INFORMATION!JThis function adds a node registration to a directory service, or modifiesa Kcurrent node registration. HWhen the node name is entered, it is checked to see if it already existsAin the directory service. If it does not yet exist, a message isGdisplayed indicating that a new node is being registered. This featureFis used when a new node is made available in the network, and the nodeHregistration needs to be added to a directory service to allow lookup by other nodes.GIf the node name already exists, a message is displayed indicating thatHthe node name is beingL modified, and the currently registered values are'read and presented as inout defaults. !2 Directory_Service!AThis field specifies the directory service that contains the node6registration to be shown. The service must be one of: LOCAL DECDNS PHASEIVCThe service type can be abbreviated, as long as the abbreviation isunique.! 2 Node_Name!HThis field specifies the name of the nodes to be registered or modified.CThis must be the fully specified name foMr the node in the directoryservice.EThe syntax of a fully specified name depends on the directory service8being used. Examples of fully specified names might be: For Local: MailHub' For DECdns: MyCo:.Sales.MailHub For Phase IV: MLHUB! 2 Synonym!AThis field specifies the Phase IV synonym for the node. Phase IV<synonyms can be used in place of fully specified node names,Cparticularly with applications that do not support full node names.DThe synonyNm must be from 1 to 6 letters (A to Z) or digits (0 to 9),Ewith at least one letter. If the field is left blank, a synonym nameis not registered for the node.!2 Address_Towers!DThis field allows you to indicate how you want to handle the addressEtowers for the node registration. You can enter one of the followingCkeywords. These can be abbreviated, as long as the abbreviation isunique.0 Modify - Modify the current address towers.G If the node is being regOistered, this allows you to enter! new address towers.I If the node is being modified, the old towers are presentedE as defaults, and you can change, add, or delete address tower information.. Keep - Keep the current address towers.H If the node is being registered, it has no current towers.F Use this to indicate that no towers are to be registered for the node.G If the P node is being modified, the current address towers remain unchanged.1 Replace - Replace the current address towers.G If the node is being registered, this allows you to enter@ new address towers (this is equivalent to modify).C If the node is being modified, the current towers areF deleted, and you are asked for a new set of towers to be& registered for the node.0 Delete - Delete the current add Qress towers.H If the node is being registered, it has no current towers.D This indicates that no towers are to be registered for4 the node (this is equivalent to keep).C If the node is being modified, the current towers areB deleted. You are not asked for a new set of towers.DIf you answer replace or modify, another form is brought up to allow+you to enter the address tower information.AIf you answer keep or delete, yoRu are asked if the node should beCregistered or modified. You can proceed or cancel the operation at this time.! wwu1 REGISTER_NODE_TOWERS!FThis form is displayed when you register or modify a node, and specifyIthat the address towers are to be either modified or replaced. It allowsGyou to delete existing towers, to modify towers, and to add new towers.! 2 Address!DThis field is used to specify an address for the node. If there are4no more addresses to S define, leave this field blank.JThe address can be either an NSAP value or a Phase IV address value. If aIPhase IV address is specified, an NSAP is constructed using the specifiedHaddress and the Phase IV prefix value. The N-Sel value is assumed to be"20" (for NSP).Some examples of addresses are:H 1.5 - A Phase IV address (using the default Phase IV prefix)H 1.5+39:840 - A Phase IV address (using an explicit Phase IV prefix)D 39:840:01:AA0004000504:20 - An NSATP with an N-Sel indicating NSPD 39:840:01:AA0004000504:21 - An NSAP with an N-Sel indicating TP4BSee the MAIN_MENU NSAP_ADDRESSES and PHASE_IV_ADDRESSES topics for!details about entering addresses.!! 2 Transport!?This field is used to specify the Transport version to use when.connecting to this node. This must be either:: TP4 - Use TP4 with the default DECnet T-Sel (DEC0)4 TP4=tsel - Use TP4 with the specified T-Sel value NSP - Use NSPIIf the N-Sel in Uthe node address field is "20", this must be NSP. If the+N-Sel is any other value, this must be TP4.GIf using a T-Sel value other than "DEC0", it must be specified after anCequals sign. The T-Sel value must be an even number of hexadecimalEdigits (if an odd number of digits is supplied, a "0" is added to theend).! 2 Another!DThis field allows you to indicate whether or not to define any more address towers.IIf you answer yes, you start with the address field again. If yVou answerHno, you are asked if the node should be registered or modified. You can-proceed or cancel the operation at this time.! wwu1 UPDATE_NODE_INFORMATION!FThis function updates the addressing information for a registered nodeCin a directory service. It reads the node's addressing informationGdirectly from the node, using network management, and modifies the node.registration to contain the correct addresses.IIf an explicit node name is entered, the addre Wss 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 DireXctory_Service!AThis field specifies the directory service that contains the node8registration to be updated. The service must be one of: LOCAL DECDNS PHASEIVCThe service type can be abbreviated, as long as the abbreviation isunique.! 2 Node_Name!GThis field specifies the name of the node to be updated. The node namecan be one of:C The fully specified name for the node in the directory service.& The Phase IV synonym for the node.EThe syntax oYf a fully specified name depends on the directory service8being used. Examples of fully specified names might be: For Local: MailHub' For DECdns: MyCo:.Sales.MailHub For Phase IV: MLHUB?An example of a Phase IV synonym for any of the above might be: MLHUBBWildcards are allowed in the node name using an asterisk (*). Forexample: For Local: Mail*% For DECdns: MyCo:.Sales.Mail* For Phase IV: ML*FThe wildcard character can Z come anywhere in the last part of the name.,Only a single wildcard character is allowed.!2 Remote_or_Local!EIf an explicit node name is entered, with no wildcard characters, theEnode can be identified as being remote or local. The following fieldGvalues are allowed, and can be abbreviated, as long as the abbreviation is unique.G REMOTE Indicates that the node to be updated is a remote node. InI this case, a node address must be supplied in the appropriateH [ field, and a remote network management connection is used to- obtain the node's full tower set.H LOCAL Indicates that the node to be updated is the local node. InG this case, a local network management connection is used toI obtain the node's full tower set. There is no need to supply a node address.IIf this field is left blank, a default of REMOTE is assumed. If the nodeDname contains a wildcard character, the value must alw\ays be REMOTE.!2 Node_Address!CThis field is used to specify an address to use when establishing aAnetwork management connection to the node. This parameter can beDspecified 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 G]An 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:/ DNA format: 39:840:0001:AA-00-04-00-05-04:00' OSI format: 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.EThe Phase IV prefix value can be specified with the Phase IV address,/or set as a default using the preferences form.(Examples of a Phase IV address might be:E 1.5 Uses the default Phase IV prefixE 1.5+39:840 Uses an explicit Phas_e IV prefixGIf a value is not specified, the currently registered addresses for theEnode are tried. If none of these result in a connection, an error is reported.! wwu 1 RENAME_NODE!KThis function changes the name of a registered node 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 funct`ion only changes the name in the directory 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 Directory_Service!GThis field specifies the directory service that contains the node to be%renamed. The service must be one of: LOCAL DECDNS PHASEIVCThe service type can be abbreviated, as long as the abbreviation isunique.!2 Old_Node_Name!GThis field specifiesa the name of the node to be renamed. The node nameGmust be the fully specified name for the node in the directory service.EThe syntax of a fully specified name depends on the directory service8being used. Examples of fully specified names might be: For Local: MailHub' For DECdns: MyCo:.Sales.MailHub For Phase IV: MLHUBWildcards are not allowed.!2 New_Node_Name!JThis field specifies the new name for the node. The new node name must be0a fully specbified name in the directory service.EThe syntax of a fully specified name depends on the directory service8being used. Examples of fully specified names might be: For Local: MailHub' For DECdns: MyCo:.Sales.MailHub For Phase IV: MLHUBWildcards are not allowed.! 2 New_Synonym!EThis field specified the new Phase IV synonym for the node. Phase IVIsynonyms can be used in place of fully specified node names, particularly6with applications that do not sucpport full node names.DThe synonym must be from 1 to 6 letters (A to Z) or digits (0 to 9),with at least one letter.FThis is initially filled in with the current synonym value, but can be?changed to a new synonym, or left blank to indicate no synonym.! wwu 1 REPAIR_NODE!GThis function repairs the synonym and reverse address mapping links fornodes in a directory service.GThis function is used when a node's synonym and reverse address mappingJlinks are acdcidentally deleted or otherwise changed to that they no longerKmap to the correct node name. To determine whether or not a node's synonymIand reverse address mapping links are correct, use the show function withthe full format.!2 Directory_Service!GThis field specifies the directory service that contains the node whose6links are to be repaired. The service must be one of: LOCAL DECDNS@The Phase IV database does not require or use synonym or reverseEaddress mapping elinks. This command does not apply to this directoryservice.CThe service type can be abbreviated, as long as the abbreviation isunique.! 2 Node_Name!DThis field is not used when repairing the Local Naming Database. Itis used only for DECdns.IThis field specifies the name of the node whose links are to be repaired.BThe node name must be the fully specified name for the node in thedirectory service.EThe syntax of a fully specified name depends on the directory service8fbeing used. Examples of fully specified names might be:' For DECdns: MyCo:.Sales.MailHubBWildcards are allowed in the node name using an asterisk (*). Forexample:% For DECdns: MyCo:.Sales.Mail*FThe wildcard character can come anywhere in the last part of the name.,Only a single wildcard character is allowed.@The Phase IV database does not require or use synonym or reverseEaddress mapping links. This functon does not apply to this directoryservice.! wwgu1 DEREGISTER_NODE_INFORMATION!GRemove a node registration from a directory service. This is used whenGa node is no longer available in the network, and the node registration-needs to be removed from a directory service.!2 Directory_Service!AThis field specifies the directory service that contains the node=registration to be deregistered. The service must be one of: LOCAL DECDNS PHASEIVCThe service type can be abbreviated, as long as the abhbreviation isunique.!2 Node_Name_or_Address!HThis field specifies the identification of the nodes to be deregistered.&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!GThe node to be deregistered cain 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: MailHub' For DECdns: MyCo:.Sales.MailHub For Phase IV: MLHUB?An example of a Phase IV synonym for any of the above might be: MLHUBBWildcards are allowed in the node name using an asterisk (*). Forexample: For Local: Mail*% For DECdns: j MyCo:.Sales.Mail* For Phase IV: ML*FThe wildcard character can come anywhere in the last part of the name.,Only a single wildcard character is allowed.! 3 Addresses!FThe node to be deregistered 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 convkerted to anNET before it is used.9 DNA format: ::-::005 OSI format: +00Examples of NETs might be:/ DNA format: 39:840:0001:AA-00-04-00-05-04:00' OSI format: 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. lEThe Phase IV prefix value can be specified with the Phase IV address,/or set as a default using the preferences form.(Examples of a Phase IV address might be:E 1.5 Uses the default Phase IV prefixE 1.5+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 am 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 Display_Node_Information!HThis field allows you to see the list of nodes to be deregistered before"the actual deregistration is done.IIf you answer no, you are immediately asked ifn the specified nodes are to8be deregistered, or if the operation is to be cancelled.HIf you answer yes, you are presented with the names and addresses of theInodes, before you are asked if the nodes are to be deregistered or if theoperation is to be cancelled.! wwdv1 EXPORT_NODE_INFORMATION!JThis function extracts node registration information for some set of nodesIand writes it to a text file. Once the information has been exported, itcan be:7 - Used fo or 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 directory service, using the VERIFYp! feature of the IMPORT command.F - Used to remove node information from a directory service, using the, DEREGISTER feature of the IMPORT command.!2 Directory_Service!AThis field specifies the directory service that contains the node9registration to be exported. The service must be one of: LOCAL DECDNS PHASEIVCThe service type can be abbreviated, as long as the abbreviation isunique.!2 Node_Name_or_Address!DThis field specifies the identificatqion of the nodes to be exported.&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!CThe node to be exported can be specified using its full name or itsPhase IV synonym.EThe syntax of a fully specified namer depends on the directory service8being used. Examples of fully specified names might be: For Local: MailHub' For DECdns: MyCo:.Sales.MailHub For Phase IV: MLHUB?An example of a Phase IV synonym for any of the above might be: MLHUBBWildcards are allowed in the node name using an asterisk (*). Forexample: For Local: Mail*% For DECdns: MyCo:.Sales.Mail* For Phase IV: ML*FThe wildcard character can come anywhere in the lasst 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 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 tformat: +00Examples of NETs might be:/ DNA format: 39:840:0001:AA-00-04-00-05-04:00' OSI format: 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.EThe Phase IV prefix value can be specified with the Phase IV address,/or set as a default using the pr ueferences form.(Examples of a Phase IV address might be:E 1.5 Uses the default Phase IV prefixE 1.5+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 idvH 39:840:* (or 39840+*) Wildcard the local area and node id9 1.* Wildcard the node idB *.* Wildcard the area and node id! 2 File_Name!FThis field specifies the name of the text file to contain the exported information.HSee the MAIN_MENU EXPORT_FILE topic for more information on the contents of this file.! wwdv1 IMPORT_NODE_INFORMATION!GThis function uses exported node registrwation information, contained inGa text file created by the export function or by a text editor, to helpmaintain a directory service.!2 Directory_Service!JThis field specifies the directory service to import the node registration"into. The service must be one of: LOCAL DECDNS PHASEIVCThe service type can be abbreviated, as long as the abbreviation isunique.! 2 File_Name!IThis field specifies the name of the text file that contains the exportednodex information.HSee the MAIN_MENU EXPORT_FILE topic for more information on the contents of this file.!2 Error_File_Name!EThis field specifies the name of a file to receive any error reports.DAn error file is useful since the import function 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 IMP yORT 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 Template!AThis field specifies how the "name" field in the export file node!registration information is used.GThe 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 zservice. 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 that indicates what the fully specified name is toElook like, with an asterisk (*) where the terminating name goes. Forexample: Local: * DECdns: MyCo:.Sales.*CIf lef {t blank, 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.ISee the MAIN_MENU EXPORT_FILE topic for descriptions of the name template9control line and the node registration information lines.! 2 Function!HThis field allows you to specify the type of import function to perform.*The following function types are provided.G Update - Regis |ter the nodes into the directory service if they doH not already exist, or modify them if they do exist. ThisF provides a way to make changes in one directory serviceA based on information in another directory service.G Register - Register the nodes into the specified directory service.G Modify - Make bulk changes to the nodes in the directory service.G This provides a way to make a large number of synonym orF } tower changes at one time. For example, change the IDP$ values for all nodes.H Replace - Deregister any nodes that use the same synonyms or towersD as the imported nodes, and then register the importedH nodes into the directory service. this provides a way to? make a large number of name changes at one time.? Deregister - Deregister the nodes from the directory service.I Verify - Check whether or not the node informa~tion in the directoryB service matches the information in the export file.! ww(Dv1 SET_PREFERENCES!IThis form allows you to set preferred values to use for various defaults,Jsuch as the reverse address mapping directory name to use for a particulardirectory service.GIt is particularly useful to set these defaults using a DECNET_REGISTERCinitialization command file, so that they will set up automatically&every time DECNET_REGISTER is started.HSee the MAIN_MENU INITIALIZATION_COMMAND_FILE topic for more information#about initialization command files.!2 Directory_Service!CThis field specifies the directory service to use immediately afterAstartup. The directory service can be changed when executing any function.The service must be one of: LOCAL DECDNS PHASEIVCThe service type can be abbreviated, as long as the abbreviation isunique.!2 Phase_IV_Address_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 is;specified for a node identification or in an address tower.IFor example if the Phase IV address is "1.5", a Phase IV prefix value of: 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:20GIf any Phase IV addresses require the use of some Phase IV prefix otherHthan the value set using this field, they can be specified using a PhaseHIV address syntax that includes the Phase IV prefix. This will override7the default value specified in this form. For example: 1.5+39:840:800AB79DSee the MAIN_MENU PHASE_IV_PREFIXES topic for details about Phase IVprefix values.! 2 NSAP_Format!DThis specified the format to use when converting NSAP addresses to aBtext representation. You can enter one of the following keywords.@These can be abbreviated, as long as the abbreviation is unique. DNA - Use DNA text format OSI - Use OSI text formatThese formats are:? DNA format: ::-::; OSI format: + For example:1 DNA format: 39:840:0001:AA-00-04-00-05-04:20) OSI format: 39840+0001AA000400050420!2 Synonym_Directory!EThis specifies the base directory or name entry to use when accessing9synonym mapping links in the specified directory service.CThe links under this directory are used to map Phase IV synonyms to@their respective node names. These are used only for the DECdnsdirectory service.FSee the MAIN_MENU NAMES_AND_DIRECTORIES SYNONYM_MAPPING topic for more!information on these directories.!2 Reverse_Address_Directory!EThis specifies the base directory or name entry to use when accessingEreverse address mapping links (also called back translation links) in the specified directory service.CThe links under this directory are used to map NSAP values to theirDrespective node names. These are used only for the DECdns directoryservice.ESee the MAIN_MENU NAMES_AND_DIRECTORIES REVERSE_ADDRESS_MAPPING topic*for more information on these directories.!! ww(Dv1 MANAGE_DIRECTORIES!HThis form allows you to execute the appropriate management procedure for the specified directory service.FThe management procedures only provides management of those aspects ofEthe directory service that affect how node names are stored and 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!JThis field specifies the directory service to manage. The service must beone of: DECDNSCThe service type can be abbreviated, as long as the abbreviation isunique.EThe Local and Phase IV databases do not require any directory serviceFmanagement functions. This function does not apply to these directory services.ww