DECNET_REGISTER_COMMANDS.HLB  —  UPDATE
 Update a node's addressing information in a directory service.

     UPDATE [DECNET] NODE node-name
         [ DIRECTORY_SERVICE dir-service ]
         [ ADDRESS addr-value ]
         [ PHASEIV_PREFIX addr-prefix ]
         [ REVERSE_DIRECTORY rev-dir-name ]

 This reads a node's addressing information directly from the node, using
 network management, and modifies the node registration to contain the
 correct addresses.

 If an explicit node name is entered, the address to use to connect to the
 node can also be explicitly entered.  If an address is not specified, the
 currently registered addresses for the node are tried.  If none of these
 result in a connection, an error is reported.

 If the node name contains a wildcard, an address cannot be specified.  In
 this case, the currently registered addresses for each matching node name
 are tried.  If none of these result in a connection for a particular node,
 an error is reported for that node.

1  –  NODE 

 This specifies the name of the new node to be registered.

     NODE node-name

 The node identification can be one of:

     The fully specified name for the node in the directory service.
     The Phase IV synonym for the node.

 The syntax of a fully specified name depends on the directory service
 being used.  Examples of fully specified names might be:

     For Local:      NODE MailHub
     For DECdns:     NODE MyCo:.Sales.MailHub
     For Phase IV:   NODE MLHUB

 An example of a Phase IV synonym for any of the above might be:

     NODE MLHUB

 Wildcards are allowed in the node name using an asterisk (*).  For
 example:

     For Local:      NODE Mail*
     For DECdns:     NODE MyCo:.Sales.Mail*
     For Phase IV:   NODE ML*

 The wildcard character can come anywhere in the last part of the name.
 Only a single wildcard character is allowed.

2  –  DIRECTORY_SERVICE 

 This specifies the directory service the node is to be updated in.

     DIRECTORY_SERVICE dir-service

 The service must be one of:

     DIRECTORY_SERVICE LOCAL
     DIRECTORY_SERVICE DECDNS
     DIRECTORY_SERVICE PHASEIV

 If not specified, the default service type is used.  This default can be
 displayed or changed using the SHOW or SET DEFAULT commands.

3  –  ADDRESS 

 This specifies an address to use when establishing a network management
 connection to the node.  This parameter can be specified only if an
 explicit node name is entered, with no wildcard characters.

 Once the connection is established, the node's tower set is obtained
 and is used to update the directory service entry.

 The address value can be one of:

     One of the node's NET or NSAP addresses
     The node's Phase IV address
     The keyword "LOCAL" (or "0")

 An NET is an NSAP address value with an N-Sel value of "00" (indicating
 that it is independent of the type of transport service in use on the
 node).  If you specify an NSAP instead of an NET, it is converted to an
 NET before it is used.

   DNA format:  <afi>:<idi>:<predsp>-<locarea>:<nodeid>:00
   OSI format:  <afi><idi>+<predsp><locarea><nodeid>00

 Examples of NETs might be:

   DNA format:  ADDRESS 39:840:0001:AA-00-04-00-05-04:00
   OSI format:  ADDRESS 39840+0001AA000400050400

 If the node has a Phase IV address, that can be used instead of an NET.

   Format:      <area>.<nodeid>
                <area>.<nodeid>+<prefix>

 This is internally converted to an NET, using the Phase IV prefix value.
 The Phase IV prefix value can be specified with the Phase IV address or
 the PHASEIV_PREFIX parameter, or set using the SET DEFAULT command.

 Examples of a Phase IV address might be:

   ADDRESS 1.5                        !Uses the default Phase IV prefix
   ADDRESS 1.5+39:840                 !Uses an explicit Phase IV prefix
   ADDRESS 1.5 PHASEIV_PREFIX 39:840  !Uses an explicit Phase IV prefix

 If the node whose directory service entry is to be updated is the local
 node, use "LOCAL" (or "0").  This will force the use of a local network
 management connection.  For example:

   ADDRESS LOCAL
   ADDRESS 0

 If not specified, the currently registered addresses for the node are
 tried.  If none of these result in a connection, an error is reported.

4  –  PHASEIV_PREFIX 

 This specifies the AFI, IDI, and preDSP to use when constructing an
 NSAP from a Phase IV address.  This is used when a Phase IV address
 is specified in the ADDRESS parameter.

   PHASEIV_PREFIX addr-prefix

 For example:

     ADDRESS 1.5 PHASEIV_PREFIX 39:840:800AB738

 would result in the following NSAP being used to represent the DECnet
 Phase IV address:

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

 An alternate way of expressing this would be:

     ADDRESS 1.5+39:840:800AB738

 If not specified, the default Phase IV prefix is used.  This default can
 be displayed or changed using the SHOW or SET DEFAULT commands.

 See the PHASE_IV_PREFIXES topic for details about Phase IV prefix values.

5  –  REVERSE_DIRECTORY 

 This specifies the base directory or name entry to use when creating
 the reverse address mapping links to the node name (also called the
 back translation links).

     REVERSE_DIRECTORY rev-dir-name

 The links under this directory are used to map NSAP values to their
 respective node names.  These directories are used only for the DECdns
 directory service.

 If not specified, the default reverse directory is used.  This default
 can be displayed or changed using the SHOW or SET DEFAULT commands.

 For more information, please refer to the NAMES_AND_DIRECTORIES topic.
Close Help