HP OpenVMS Systems Documentation

Using the decnet_register tool's export and import functions, you can transfer name and addressing information between different namespaces, including:

• To or from a Phase IV local node's database
• To or from a DECdns distributed namespace
• To or from the new local namespace

See Section 5.3.9.3 for information on moving information from a Local Naming Option (LNO) database.

Use the decnet_register tool export command to create an export/import file. The following is an example export/import file created for a local namespace:

!
! DECnet-Plus node name export/import file     8-AUG-1995 11:53:24.16
!

=Type DECnet Node
=Version 1

=All        Address Prefix               49::

=DECdns     Name Template                ???:.???.*
=DECdns     Synonym Directory            ???:.???
=DECdns     Reverse Address Directory    ???:.???

=PhaseIV    Name Template                *

=LocalFile  Name Template                LOCAL:.*

TOYBOAT                          TOY    {Tower=SC2/NSP/CLNS=41.619}
TOPAZ                            TOPAZ  {Tower=SC2/NSP/CLNS=40.251}
TROY                             TROY   {Tower=SC2/NSP/CLNS=59.202}
TROUBLE                          TROUBLE{Tower=SC2/NSP/CLNS=31.121}

During network configuration on OpenVMS systems, NET$CONFIGURE.COM creates an export/import file when it determines that your node is not yet completely registered in either DECdns or the local namespace. Then, NET$CONFIGURE.COM can use the export/import file to register your node in the name service. It names the export/import file SYS$MANAGER:DECNET_REGISTER_IMPORT_FILE_SYNONYM .TXT where SYNONYM is the synonym for your node.

The system administrator can make changes to the information contained in the namespace by editing the export/import file with any text editor before importing the export/import file into a name service. The following import command functions are available:

• import register --- Registers the listed nodes into the specified name service.
• import modify --- Makes changes to the node information in the name service. This makes it possible to make a large number of synonym or tower changes at one time.
• import update --- Registers the listed nodes into the name service if they do not already exist, or modifies them if they do exist. This makes it possible to make changes in one name service based on the information from another name service.
• import replace --- Deregisters any nodes that use the same synonyms or towers as the listed nodes. Then registers the listed nodes in the name service. This makes it possible to make a number of name changes at one time.
• import verify --- Checks whether or not the information in the name service matches the listed nodes.
• import deregister --- Deregisters the listed nodes from the name service.

Select Option 7 at the decnet_register main menu to create a text file that can be edited and contains the node information extracted from the name service.

Export node information
  Use Return, Ctrl-N, and Ctrl-P to move between input fields
  Use "?" to obtain help, Ctrl-Z to cancel

Specify the directory service as LocalFile, DECdns, or PhaseIV.

* Directory service: LocalFile

Specify the node names to export using a wildcard name, NSAP, Phase IV
synonym, or Phase IV address.

* Node name or address: T*

Specify the file name to export data into.

* File name: export_nodes.txt

Press Return to export, Ctrl-Z to cancel
Exporting node name information using: T*
1) LOCAL:.TOYBOAT
2) LOCAL:.TOPAZ
3) LOCAL:.TROY
4) LOCAL:.TROUBLE

Select Option 8 at the decnet_register main menu to import the node information contained in a text file in to a name service.

Import node information
  Use Return, Ctrl-N, and Ctrl-P to move between input fields
  Use "?" to obtain help, Ctrl-Z to cancel

Specify the directory service as LocalFile, DECdns, or PhaseIV.

* Directory service: LocalFile

Specify the file containing the data to import into the directory service.
Specify the error log file (if none, errors go to the terminal).

* Data file name:  export_nodes.txt
* Error file name:

Specify the name template, with "*" where the node names should be inserted.
Specify the function as either update, register, modify, replace, deregister,
or verify.

* Template: *
* Function: verify

Press Return to import, Ctrl-Z to cancel

Directory Service: Local name file
Verifying nodes listed in export_nodes.txt

1) TOYBOAT
2) TOPAZ
3) TROY
4) TROUBLE

DECnet-Plus includes a local namespace that replaces functionality previously provided by the LNO namespace, the DECdns Local Naming Option.

The decnet_register_lno tool translates an existing LNO text file into a new local namespace file.

Run decnet_register_lno with the following command:

$ mcr sys$system:decnet_register_lno

This tool is supplied for backward compatibility only. You must have an existing LNO text file to use this procedure.

5.3.10 Setting Preferences and Network Values

Select Option 9 at the decnet_register main menu to preset values for the most commonly used decnet_register parameters and to establish parameter values for the remainder of your current decnet_register session. By including a set default command in your decnet_register initialization command file, as explained in Section 5.3.11, you can preset parameter values before the session begins.

Set preferences and network values
  Use Return, Ctrl-N, and Ctrl-P to move between input fields
  Use "?" to obtain help, Ctrl-Z to cancel

Specify the directory service as LocalFile, DECdns, or Phase IV.

* Directory service:

Settings applicable to any directory service.

* Phase IV address prefix:

* NSAP format (DNA or OSI):

Settings applicable to the specific directory service.

* Synonym directory:

* Reverse address directory:
Press Return to set the values, Ctrl-Z to cancel

For help answering the prompts, refer to the following:

Directory Service

Enter a directory service keyword: Local, DECdns, or PhaseIV.

Phase IV Address Prefix

Enter the AFI (authority and format identifier), IDI (initial domain identifier), and preDSP (domain-specific part) to use when constructing an NSAP from a Phase IV address. For example, the Phase IV address 1.5 and the Phase IV prefix 39:840:800AB738 result in the following NSAP address:

39:840:800AB738-0001:AA-00-04-00-05-04:20

NSAP Format

Enter an NSAP format keyword: DNA or OSI to use when converting an NSAP address to a text representation.

DNA specifies DNA text format:

<afi>:<idi>:<predsp>-<locarea>:<nodeid>:<nsel>

OSI specifies OSI text format:

<afi><idi>+<predsp><locarea><nodeid><nsel>

Synonym Directory

For the DECdns name service, enter the synonym directory name to use when a decnet_register command does not specify a synonym directory.

Reverse Address Directory

For the DECdns name service, enter the reverse address (or backtranslation) directory name to use when a decnet_register command does not specify a backtranslation directory.

5.3.11 Using an Initialization Command File for Preset Values

When it starts, the decnet_register attempts to execute an initialization command file if one is present. By including a set default command in your decnet_register initialization command file, you can preset parameter values before your decnet_register session begins.

On OpenVMS systems, decnet_register looks for the following default initialization file:

sys$login:decnet_register.ini

If this file is found, it is executed as a command file containing decnet_register commands.

To use a different file name, specify a logical definition as follows with initialization-command-file naming your command file:

$ define decnet_register_init

This section contains instructions for initializing the DECdns distributed namespace using the decnet_register manage command to invoke the decnet_register_decdns command or script file. This section describes how to perform the following namespace tasks:

• Creating the namespace directories required by DECnet-Plus (Do this once per network, immediately after creating the namespace.)
• Creating other directories in the namespace
• Replicating directories
• Creating access control groups and adding, removing, and showing members of an access control group
• Initializing the DNA_Registrar access control group, and adding and removing members from the DNA_Registrar access control group
• Changing the security level of directories in the namespace to allow or disallow nodes to automatically register themselves in the namespace when they are configured

To perform certain tasks discussed in this chapter, you need access rights. For more information about the access rights, refer to the DECnet-Plus DECdns Management guide. Also, DECnet-Plus DECdns Management contains complete information about DECdns and the namespace and provides namespace planning information.

Initializing the DECdns namespace consists of creating the backtranslation and node synonym directories, and the required DECdts directory DTSS_GlobalTimeServers. Some DECnet features do not work properly unless these directories exist; for example, you cannot use Phase IV node names if the node synonym directory (usually .DNA_NodeSynonym) is not available.

Every DECdns namespace must be initialized for DECnet use at least once. This involves creating required namespace directories and the .DNA_Registrar access control group. On OpenVMS systems, the namespace is initialized when the DECnet-Plus advanced configuration procedure creates the namespace. On DIGITAL UNIX systems, you create and initialize a namespace independently of the configuration procedure by using dnsconfigure.

To create directories and access control groups, you need to have access to the clearinghouses and directory in which you want to create these directories and groups. You usually do this from the node and account that created the namespace.

You can reinitialize the namespace for DECnet at any time; if the namespace directories already exist, the tool does not overwrite them. You need to reinitialize the namespace if, for example, a backtranslation directory was accidentally deleted.

Initialization creates the following directories:

• Backtranslation directory
  Translates an address to a name. This directory contains one child directory for each IDP (initial domain part) and preDSP in the network. Each of these child directories contains one child directory for each local area defined within that IDP and preDSP. Each local area child directory contains one soft link for each node ID defined in that local area. This is usually called .DNA_BackTranslation directory.
  The decnet_register tool creates the soft link for each Phase IV node when you register the node using either Option 2 or Option 8 on the main menu form.
  When you specify that the network contains Phase IV nodes, this function automatically creates the address backtranslation directories required for registering Phase IV nodes. You can create address backtranslation directories manually by selecting Function 3 on the decnet_register_decdns function menu.
• Node Synonym directory
  Translates a Phase-IV-compatible node name (called a Phase IV node synonym) to a DECnet Phase V node full name. This directory contains a soft link for each node that has a Phase IV node synonym. This is usually called the .DNA_NodeSynonym directory.
  The decnet_register tool automatically creates synonym soft links for nodes when you register the nodes using either Option 2 or Option 8 on the main menu form.
• .DTSS_GlobalTimeServers
  Holds the names and network locations of global time servers for DECdts.

Initialization also creates the access control group .DNA_Registrar. This access control group contains a list of network users with read, write, delete, test, and control access to all namespace objects, soft links, and directories created using decnet_register and decnet_register_decdns.

To initialize the namespace for a DECnet-Plus for OpenVMS system, select Option 10 on the decnet_register main menu. The following messages and prompts appear, one by one. Enter decdns as the name service to manage. Enter ? for help. Press the appropriate control key sequence for your platform to cancel the initialization. Output is similar to the following example (from an OpenVMS system):

Manage the node name storage aspects of a directory service
  Use Return, Ctrl-N, and Ctrl-P to move between input fields
  Use "?" to obtain help, Ctrl-Z to cancel
Specify the directory service as DECdns.
* Directory Service: decdns
This function executes the "SYS$MANAGER:DECNET_REGISTER_DECDNS.COM"
procedure to
perform management of only those aspects of the directory service
that affect the storage of node name data.

Press Return to execute the procedure, Ctrl-Z to cancel

Starting the directory management procedure for the DECdns directory service
The procedure name is "@SYS$MANAGER:DECNET_REGISTER_DECDNS.COM"

DECnet-Plus node directory management for DECdns

Type a question mark (?) at any prompt to obtain help.
Press Ctrl-Z at any prompt to exit from the function.

Enter the name of the DECdns namespace to use.
The default is the system default namespace (bb_ns:).

* Namespace name: bb_ns

Checking the bb_ns namespace.

Choose one of the following functions by specifying its function number,
or request help by typing HELP or a question mark (?).


 0 - Exit

 1 - Create a directory to hold registered node names
 2 - Create a directory for Phase IV Synonyms
 3 - Create a directory for address-to-name translations
 4 - Create the directory for the DECdts Time Services

 5 - Replicate a node name or synonym directory
 6 - Replicate an address-to-name translation directory

 7 - Create an access control group
 8 - Add members to an access control group
 9 - Remove members from an access control group
10 - Show members of an access control group

11 - Allow node autoregistration into a directory
12 - Disallow node autoregistration into a directory

* Function to execute:

Your namespace will probably include many directories in which nodes are registered. Only the smallest networks should have all nodes registered in the root directory. For a more detailed discussion of this strategy, refer to the DECnet-Plus DECdns Management guide.

To create a directory, select Option 10 at the decnet_register main menu. Enter decdns as the name service to manage and enter the name of the DECdns namespace to use. Then select Function 1 from the decnet_register_decdns function menu.

These prompts appear, one by one. Press the appropriate control key sequence for your platform to exit. Output is similar to the following example:

Create additional directories for registering node names.
Press Ctrl-Z when done.

* Directory name: .xyz

Enter the name of the clearinghouse for the master copy of the directory.
The default is the parent directory's clearinghouse.

* Master replica clearinghouse: .mgv460_bb_ch

Enter the names of the access control groups to apply to the directory,
separated by commas.
The default is no access control groups.

* Access control groups: .worldread_group

Creating the bb_ns:.xyz directory.

For help answering the prompts, refer to the following:

Directory Name

Specify the full name for the directory to be created. This should not include a node or user name; for example, .Japan.Osaka.

Master Replica Clearinghouse

Specify the name of the clearinghouse where the master directory replicas should be created. Include any required directory information; for example, if your clearinghouse is in the root directory, you might type .MAS_CH.

If you do not specify a clearinghouse name, the parent directory's clearinghouse is used (this is the DECdns default).

Access Control Groups

Enter the names of one or more DECdns access control groups that you want to include in the access control set for the directory (or directories) you create. Using groups other than .DNA_Registrar allows you to control user access to the directories by listing those users who have read, write, delete, test, and control access to directories created using decnet_register_decdns. The specified access control groups are propagated to all node names registered in the created directories.

To specify more than one group name, separate them by commas.

The .DNA_Registrar group is included automatically in the list, whether or not you specify it.

The .DNA_Registrar group is created and populated by decnet_register_decdns. You are responsible for creating and populating any additional groups that you specify.

After you have answered all the prompts, decnet_register_decdns displays messages as it creates the directories. Press the appropriate control key sequence for your platform to exit. Output is similar to the following example:

* Directory name: .xyz

* Master replica clearinghouse: .mgv460_bb_ch
* Access control groups [Def=DNA_Registrar]: .worldread_group

Creating the bb_ns:.xyz directory.

* Directory name:

When you initialize the namespace for DECnet use, the tool creates backtranslation directories in the namespace for your network IDP and preDSP and for each network area that you specify. If you add an IDP, preDSP, or network area to your network, you must create new backtranslation directories. Also, if you plan to change the network's IDP or preDSP or a node's area, first create new backtranslation directories.

To create a directory for a new DECnet area or IDP and preDSP, select Function 3 at the decnet_register_decdns function menu. The following prompts appear, one by one. Press the appropriate control key sequence for your platform to exit.

Output is similar to the following example:

Create a directory tree to hold address-to-name translation information.
Press Ctrl-Z when done.

Enter the name of the base address-to-name translation directory.
The current default is ".DNA_BackTranslation".

* Directory name: .DNA_BackTranslation
* Create the base directory [y/n, def=no]: y

Enter the name of the clearinghouse for the master copy of the directory.

The default is the parent directory's clearinghouse.

* Master replica clearinghouse: major2:.nyc_ch

Enter the names of the access control groups to apply to the directory,
separated by commas.

Enter "." to reset the default to no access control groups.
The current default is ".dna_registrar".

* Access control groups: .dna_registrar

Creating the MAJOR2:.DNA_BackTranslation directory.

Enter the OSI area prefix, using either of the formats:

  <afi>:<idi>:<predsp>
  <afi><idi>+<predsp>

The current default is "49::"

* OSI area prefix: 49::
* Create the OSI area prefix directory [y/n, def=no]: y

Enter the name of the clearinghouse for the master copy of the directory.

The default is the parent directory's clearinghouse.

* Master replica clearinghouse: major2:.nyc_ch

Enter the names of the access control groups to apply to the directory,
separated by commas.

Enter "." to reset the default to no access control groups.
The current default is ".dna_registrar".

* Access control groups:  .dna_registrar

Creating the MAJOR2:.DNA_BackTranslation.%X49 directory.

Enter the local area, using either of the formats:

  A decimal value, from 1 to 63
  A hexadecimal value, from %x0001 to %xFFFE

It is assumed that local area child directory needs to be created. (1)

* Local area: 4

Enter the name of the clearinghouse for the master copy of the directory.

The default is the parent directory's clearinghouse.

* Master replica clearinghouse: major2:.nyc_ch

Enter the names of the access control groups to apply to the directory,
separated by commas.

Enter "." to reset the default to no access control groups.
The current default is ".dna_registrar".

* Access control groups: .dna_registrar

Creating the MAJOR2:.DNA_BackTranslation.%X49.%X0004 directory.

Enter the local area, using either of the formats:

  A decimal value, from 1 to 63
  A hexadecimal value, from %x0001 to %xFFFE

It is assumed that local area child directory needs to be created.

* Local area:

Press the appropriate control key sequence for your platform to exit.