1 Export_File ! An export file is created using the EXPORT command. This is a text file containing node registration information read from some directory service. This file can be used as input to the IMPORT command to move node information from one directory service to another, or to verify the information in one or more directory services. It can also be edited to 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. : The directory service and node registration information sections are repeated as often as necessary to ensure that the appropriate directory service information is associated with the correct node registration information. ! 2 Type_and_Version ! This section contains the following information. Lines beginning with an equals sign (=) contain control information (the equals sign must be in the first character position, or it is treated as the first character of a node name). =Type DECnet Node =Version 1 These lines specify the file contents and version. The values shown above are the only currently recognized values. ! 2 Directory_Service_Information ! This section contains the following information. Lines beginning with an equals sign (=) contain control information (the equals sign must be in the first character position, or it is treated as the first character of a node name). =All Address Prefix ??? =DECdns Name Template ???:.???.* =DECdns Synonym Directory .??? =DECdns Reverse Address Directory .??? =LocalFile Name Template ???* =PhaseIV Name Template * The information specified in this section provides default values for use when importing into the indicated directory service ("All" indicates information that is used for all directory services). Lines from this section can be repeated further down in the file, to change the supplied information. For example, this is useful when a file contains node information that is to be registered into several directories (specified using the Name Template value). Initially, the value for each piece of information is set to "unknown", by writing question marks (???) to the file. If the EXPORT command can determine an appropriate value for any of these, it places that value in the file instead. This is possible only for the directory service you are exporting from. When the file is read by the IMPORT command, only those lines intended for the target directory service are examined. All others are ignored, and can contain invalid values without causing an error. Also, each line in this section has an equivalent IMPORT command parameter. If the parameter is specified in the IMPORT command, then the value contained in the file for that parameter is ignored, and can contain an invalid value without causing an error. See the IMPORT command for an explanation of each parameter value. ! 2 Node_Registration_Information ! This section contains the node registration information. These lines must not begin with an equals sign (=) in the first character position. If a node uses an equals sign as the first character in its name, indent the name by at least one space. The format for a node information line is: name synonym {TOWER=tower, TOWER=tower, ..., TOWER=tower} Where: name The terminating part of the name for the node. This is generally the part of the name that is the same regardless of the directory service. For example, "MailHub" is the terminating name for the following: Local: MailHub DECdns: MyCo:.Sales.MailHub When importing into the Phase IV Database, this is ignored and the synonym field used used, if a synonym is defined. If a synonym is not defined, and the name is not Phase IV compatible, an error results. synonym The Phase IV synonym for the node, if any. This is optional. tower A tower value for the node. The format for an individual tower is the same as it is in a TOWERS parameter. See the ADDRESS_TOWERS topic for a description of this format. All directory services except the Phase IV database support multiple towers. If importing into the Phase IV Database, the first Phase IV compatible tower is used. The braces surrounding the list of towers are required. For example: MailHub MLHUB {Tower=12.2, Tower=37:840:0001:08-00-2B-0D-E9-B1:21}