![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
For help answering the prompts, refer to the following:
Directory Service
Identify the name service where the node's information is stored. Name services include the local namespace, the DECdns distributed namespace, and the Phase IV database.
Node Name or Address
Enter a node name or address, as follows:
| Full name | The node's full name, including the directory or directories. You can replace all or part of any simple name in the full name, including the directory names, with a wildcard character (*) to show multiple nodes. |
| Synonym | The node's Phase IV synonym. This must not contain any directory names. You can replace all or part of the synonym with a wildcard character (*) to show multiple nodes. |
| NET or NSAP | The node's network entity title (NET), which is the node's NSAP (network service access point) with a selector field of 00 or its NSAP. You can replace the node ID field of the NET with a wildcard character (*) to show all nodes within an area. For more information about NETs, refer to your introduction and user's guide. |
| Address | The node's Phase IV address, in the format area.id. You can replace the id field of the address with a wildcard character (*) to show all nodes within an area. |
Display Format
The tool displays the node information in brief or full format or simply displays the node full name.
Output File
Enter a file name and press Return to send the output to a file. Press Return without entering a file name to display the information on the screen. Press the appropriate control key sequence for your platform to cancel the show operation.
If you specify a full name, brief format appears as follows:
Directory Service: Local name file
Node name: LOCAL:.grand.sales
Phase IV synonym: SALES
Node address: 49::00-04:AA-00-04-00-93-10:20 (4.147)
Node address: 49::00-04:AA-00-04-00-93-10:21 (4.147)
Node address: 41:45418715:00-41:08-00-2B-14-2D-47:21
Node address: 41:45418715:00-41:08-00-2B-14-2D-47:20
Number of nodes reported on: 1
Press the appropriate control key sequence for your platform to exit.
You must register all DECnet Phase V nodes and Phase IV nodes in the namespace to make them accessible to other nodes in the network.
When you register a node name, decnet_register creates a node entry by that name in the namespace you specify. For nodes in the DECdns namespace, decnet_register also creates a Phase IV synonym soft link and an address-to-name backtranslation soft link. Each object and soft link is assigned the minimally required access control. You can later add additional access control to the object manually.
To register or modify a DECnet Phase V node in the namespace, select Option 2 at the decnet_register main menu and respond to the prompts as they appear, one by one. Press the appropriate control key sequence for your platform to exit. Output is similar to the following example:
Register or modify 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 explicit name of the node to register or modify:
* Node name: sales
Attempting to look up node name
* Node name: LOCAL:.grand.sales
* Synonym: SALES
Specify how to handle the node's registered address towers, using either
modify, keep, replace, or delete. The current number of towers is "4".
* What should be done with the current address towers: Modify
Register or modify node address information
Use Return, Ctrl-N, and Ctrl-P to move between input fields
Use ? to obtain help, Ctrl-Z to cancel
The first six towers for "LOCAL:.grand.sales" are:
1) SC3/NSP/CLNS=4.147
2) SC3/TP4/CLNS=4.147
3) SC3/TP4/CLNS=41:45418715:00-41:08-00-2B-14-2D-47:21
4) SC3/NSP/CLNS=41:45418715:00-41:08-00-2B-14-2D-47:20
5) none
6) none
The address must be CLNS NSAP or DECnet Phase IV address.
The transport must be either TP4, TP4=tsel, or (Network Services Protocol)
NSP.
The Session Control version (SC2 or SC3) cannot be changed.
Tower number 1
* Address: CLNS=4.147
* Transport: NSP
* Specify another address tower (No or Yes): No
* Press Return to register the node, Ctrl-Z to cancel
For help answering the prompts, refer to the following:
Directory Service
Identify the name service where the node's information is to be registered. Name services include the local namespace, the DECdns distributed namespace, and the Phase IV database.
Node Name
Enter an explicit node name, as follows: Enter a node full name formatted for the local namespace or for DECdns, or enter a Phase IV node name. Do not include any wildcard characters.
Synonym
Enter the node's Phase IV synonym. You can replace all or part of the synonym with a wildcard character (*) to show multiple nodes.
Address Towers
Enter one of the specified keywords (modify, keep, replace, or delete) to indicate what you want to do with the node's registered address towers.
To add an address tower, specify the node's NSAP or its Phase IV address. Specify one of the following transports: TP4, TP4=tsel, or NSP.
The display continues:
Directory Service: LocalFile
Registering the node LOCAL:.grand.sales
Modifying the node synonym
Modifying the node towers
* Press Return to continue
Press the appropriate control key sequence for your platform to exit.
The update function establishes a network management connection to a node, reads the node's addressing information directly from the node, and updates the node registration to contain the correct addresses. You must specify a usable address in order to establish a network connection to the node to obtain the remainder of the addressing information.
To update addressing information for the node, select Option 3 at the decnet_register main menu and respond to the prompts as they appear, one by one. Output is similar to the following example:
Update node towers information using network management
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: decdns
Specify the node to update using an explicit or wildcard name or Phase IV
synonym. If explicitly specifying the local node name, indicate "Local",
otherwise indicate "Remote" (wildcard names must always be "Remote").
* Node name: sales
* Node is remote or local: remote
Specify the NET, NSAP, or Phase IV address to use to access the node and
obtain the node's full tower set. If you do not specify an address, an
attempt will be made to use the currently defined addresses.
* Node address: 4.147
Press Return to update, Ctrl-D to cancel
For help answering the prompts, refer to the following:
Directory Service
Identify the name service where the node's information is to be updated. Name services include the local namespace, DECdns, and the Phase IV database.
Node Name
Enter a node name, as follows:
| Full name | The node's full name properly formatted for the local namespace or DECdns. You can replace all or part of any simple name in the full name with a wildcard character (*) to show multiple nodes. Wildcard names must always be remote. |
| Synonym | The node's Phase IV synonym. You can replace all or part of the synonym with a wildcard character (*) to show multiple nodes. Wildcard names must always be remote. |
Node is Remote or Local
If the node to be updated is the local node, specify Local to force use of the local network management connection. Names that include wildcard characters must always be remote.
Node Address
The node address can be the node's network entity title (NET), which is the node's NSAP with a selector field of 00 or its NSAP, or the node's Phase IV address, in the format area.id. You can specify a node address only if you specified an explicit node name.
The display continues:
Directory Service: DECdns
Updating the tower set for "LOCAL:.grand.sales"
Number of nodes updates: 1
Number of update failures: 0
* Press Return to continue
Press the appropriate control key sequence for your platform to exit.
If the name of a node registered in the namespace changes, make sure to change the node name in the namespace.
Option 4 of decnet_register changes the name of a node in the namespace without changing any other information associated with the node name. For nodes registered in the DECdns namespace, the synonym soft link and address-to-name backtranslation soft link are updated to point to the new name. For the local namespace, this information is changed in the database.
Note
When you rename a node, you should subsequently modify any DECdns access control entry (ACE) whose principal contains the node name. If the node whose name you are changing is a DECdns server, create the new ACEs for the OpenVMS system's system account and DNS$Server account before you change the node name. If you do not create new ACEs before renaming the node, you can lock the server out of access to the namespace. For details, refer to the chapter on managing access control in the DECnet-Plus DECdns Management guide.
To change the node name, select Option 4 at the decnet_register main menu and respond to the prompts as they appear, one by one. Press the appropriate control key sequence for your platform to exit. Output is similar to the following example:
Rename a registered node
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 current name and the new name for the node. Both names must be
explicit full names.
* Old node name: Local:.hiho
* New node name: Local:.happy
Specify the Phase IV synonym to use after the node has been renamed.
Enter an asterisk (*) to keep the old synonym name. Leave the
field blank to indicate no synonym.
* New synonym: happy
Press Return to rename, Ctrl-D to cancel
For help answering the prompts, refer to the following:
Directory Service
Identify the name service containing information for the node to be renamed. Name services include the local namespace, DECdns, and the Phase IV database. Nodes can be renamed only within a name service. You cannot change the name service when renaming a node.
Old Node Name
Enter the node's current full name properly formatted for the name service.
New Node Name
Enter the node's new full name properly formatted for the name service.
New Synonym
Enter the new Phase IV synonym for the node. To keep the current synonym, enter an asterisk. To have no synonym, leave the field empty.
Directory Service: Local name file
Checking the current node registration
Renaming: LOCAL:.hiho
To: happy
* Press Return to continue
Press the appropriate control key sequence for your platform to exit.
If the synonym or reverse address mapping links for the local namespace and the DECdns name service are deleted or changed accidentally, use the repair option to restore the correct soft links. Use Option 1 of the decnet_register main menu to display the current values for a node's synonym link and reverse address mapping link.
To repair synonym or reverse address mapping links, select Option 5 at the decnet_register main menu. The tool prompts you for the name of the directory service where the node information is stored and for the name of the node whose soft links are to be repaired. Press the appropriate control key sequence for your platform to exit. Output is similar to the following example:
Repair node synonym and reverse address mapping links
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 or DECdns.
* Directory service: decdns
Specify the node to repair using an explicit or wildcard full name.
* Node name: hiho
Press Return to repair, Ctrl-Z to cancel
For help answering the prompts, refer to the following:
Directory Service
Identify the name service where synonym and reverse address mapping links need to be repaired. Specify either LocalFile or DECdns.
Node Name
Enter the node's full name properly formatted for the DECdns name service. This argument is not used for the local namespace. You can replace all or part of any simple name with a wildcard character (*) to repair multiple nodes.
The display continues:
Directory Service: DECdns
No repairs needed: Hiho
Number of nodes repaired: 0
Number not needing repair: 1
Press the appropriate control key sequence for your platform to exit.
To maximize performance, keep your namespace as up-to-date and uncluttered as possible. This includes removing obsolete node registrations from the namespace. To deregister a node from the namespace, select Option 6 at the decnet_register main menu. The tool prompts you for the node name to be removed. Press the appropriate control key sequence for your platform to exit. Output is similar to the following example:
Deregister node names
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 to deregister using an explicit or wildcard name, an NSAP,
or a Phase IV synonym or address.
* Node name or address: hiho
Specify whether or not to display node name, synonym, and NSAP information
before indicating that the nodes should or should not be deregistered.
* Display node information (no or yes):
Press Return to deregister, Ctrl-Z to cancel
For help answering the prompts, refer to the following:
Directory Service
Identify the name service where the node's information is stored. Name services include the local namespace, the DECdns distributed namespace, and the Phase IV database.
Node Name or Address
Enter a node name or address, as follows:
| Full name | The node's full name, including the directory or directories. You can replace all or part of any simple name in the full name, including the directory names, with a wildcard character (*) to show multiple nodes. |
| Synonym | The node's Phase IV synonym. This must not contain any directory names. You can replace all or part of the synonym with a wildcard character (*) to show multiple nodes. |
| NET or NSAP | The node's network entity title (NET), which is the node's NSAP with a selector field of 00 or its NSAP. You can replace the node ID field of the NET with a wildcard character (*) to show all nodes within an area. For more information about NETs, refer to your Introduction and User's Guide. |
| Address | The node's Phase IV address, in the format area.id. You can replace the id field of the address with a wildcard character (*) to show all nodes within an area. |
Display Node Information (NO or YES)
Enter NO to deregister the node without first confirming. Enter YES to see information about the node before you deregister it.
Directory Service: Local name file
Deregistering: Local:.hiho
Number of nodes deregistered: 1
Press Return to continue
Press the appropriate control key sequence for your platform to exit.
Using the decnet_register tool's export and import functions, you can transfer name and addressing information between different namespaces, including:
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:
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.
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.
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
PROFILE_VMS_004.HTML OSSG Documentation 2-DEC-1996 12:34:52.22
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.