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.