1  –  backtranslation_softlink

    Attempts to update a backtranslation softlink entity in the specified
    namespace.  In order words, the node will attempt to ensure that the
    backtranslation softlink information present in its session control
    database is consistent with the softlink information in the
    DECdns namespace.

    update  [node node-id] session control -
             backtranslation softlink softlinkname

    Normally, all the node's backtranslation softlinks are periodically
    updated in the DECdns namespace when the session control attribute
    maintain backward soft links is true.  However, if updates fail, you
    can use the DNS$CONTROL or DECNET_REGISTER tools to confirm that a
    DECdns server is accessible and that the node's object and softlinks
    are properly configured in the namespace.

    Examples:

    update session control backtranslation softlink -
       WINTER:.DNA_BACKTRANSLATION.%X49.%X0018.%XAA00040052A60
       !  Attempts to update the softlink for DECnet address 24.42
       !    in the WINTER namespace.

    update session control backtranslation softlink -
       WINTER:.DNA_BACKTRANSLATION.%XA1725E45
       ! Attempts to update the softlink for IP address
       !  161.114.94.69 in the WINTER namespace. (OpenVMS only)

2  –  tower_maintenance

    update  [node node-id] session control -
        tower maintenance DECdns_fullname

    This command attempts to update the tower information in the
    DECdns namespace.  In order words, the node will attempt to
    ensure that the address information it is currently using is
    consistent with the address information present in the DECdns
    namespace.

    Under normal conditions the towers will be automatically updated
    whenever the Session Control Address Update Interval expires or
    whenever the node experiences an address change.

    Occasionally, automatic tower maintenance updates may fail.  For
    example, updates may fail if a DECdns server is not accessible.
    In that case, the DECNET_REGISTER or DNS$CONTROL tools might then
    indicate that the towers present in the DECdns namespace are not
    consistent with the towers currently in use by the node (as seen
    by ncl show addr).  In that case, you may issue this ncl update
    command to manually correct the inconsistency after the DECdns
    server becomes available again.

    If an OpenVMS node is configured to run DECnet over IP and the
    DECdns directory service is in use, IP towers will be maintained
    in addition to NSAP towers.  However, IP tower maintenance is
    handled differently than NSAP tower maintenance due to the fact
    that there will be a period in which the IP address will be
    0.0.0.0.  In that case, none of the node's IP towers will be
    updated in the DECdns namespace until DECnet over IP has
    finished initializing and the node has learned all of its IP
    addresses (i.e., no 0.0.0.0 address remains).

    Example:

    update session control tower maintenance DEC:.LKG.TRUE
        !  Attempts to update DNA$towers attribute of the
        !  DEC:.LKG.TRUE object in the DEC namespace with
        !  all of node TRUE's current address information.