LANCP$HELP.HLB  —  SET  NODE
    Enters a node into the LAN volatile node database or modifies an
    existing entry. Requires SYSPRV privilege.

    Format

      SET NODE  node-name

1  –  Parameter

 node-name

    Supplies the name of a node to be added to the LAN volatile node
    database or an entry to be modified. Typically, the node name is
    the same as that given in the system parameter SCSNODE, but it
    does not need to be. The node name is limited to 63 characters in
    length.

2  –  Qualifiers

2.1    /ADDRESS

       /ADDRESS=node-address
       /NOADDRESS (default)

    Associates a LAN address with the node name. Specify the address
    as 6 bytes in hexadecimal notation, separated by hyphens. The
    address does not have to be unique (as might be the case when the
    address is not known, so a nonexistent address is specified).

    If multiple node addresses are to be associated with a node name,
    each combination may be given as a node name with an extension,
    for example, VAXSYS.EXA for the EXA device on node VAXSYS, or
    VAXSYS_1 for the first LAN device on node VAXSYS.

    If you do not specify the /ADDRESS qualifier, the setting remains
    unchanged. The /NOADDRESS qualifier clears the field.

2.2    /ALL

    Defines data for all nodes in the LAN volatile node database.
    If you specify a node name, all matching nodes are selected; for
    example, A/ALL selects all nodes beginning with A.

2.3    /BOOT_TYPE

       /BOOT_TYPE=boot-option
       /NOBOOT_TYPE

    Indicates the type of processing required for downline load
    requests. You can specify one of the following keywords with
    this qualifier:

    o  VAX_SATELLITE-a VAX satellite cluster boot

    o  ALPHA_SATELLITE-an Alpha satellite cluster boot

    o  I64_SATELLITE-an OpenVMS Cluster I64 satellite boot

    o  OTHER-the specified image; noncluster satellite loads that do
       not require additional data

    The distinction is necessary, because OpenVMS Cluster satellite
    loads require additional cluster-related data be appended to the
    load image given by the /FILE qualifier. The default value is
    OTHER.

    If you do not specify the /BOOT_TYPE qualifier, the setting
    remains unchanged. The /NOBOOT_TYPE qualifier clears the field.

    Note that I64 satellites boot using TFTP rather than MOP
    services. This boot type is included so that the information
    in the node database can be maintained, not because it is needed
    for booting purposes.

2.4    /DECNET_ADDRESS

       /DECNET_ADDRESS=value
       /NODECNET_ADDRESS

    Associates a DECnet address with the node name. Specify the
    address in DECnet notation, xx.xxxx.

    If you do not specify the /DECNET_ADDRESS=value qualifier, then
    the setting remains unchanged. The /NODECNET_ADDRESS qualifier
    clears the field.

2.5    /FILE

       /FILE=file-spec
       /NOFILE

    Supplies the file name of a boot file to be used when the
    downline load request does not include a file name (for example,
    OpenVMS Cluster satellite booting). The file specification is
    limited to 127 characters.

    If no file name is specified, OpenVMS Cluster satellite loads
    default to APB.EXE where the boot type is set to ALPHA and NISCS_
    LOAD.EXE where the boot type is set to VAX.

    If you do not specify the /FILE qualifier, the setting remains
    unchanged. The /NOFILE qualifier clears the field.

2.6    /IP_ADDRESS

       /IP_ADDRESS=value
       /NOIP_ADDRESS

    Associates an IP address with the node name. Specify the address
    in the standard dotted notation, xxx.xxx.xxx.xxx.

    If you do not specify the /IP_ADDRESS=value qualifier, the
    setting remains unchanged. The /NOIP_ADDRESS qualifier clears
    the filed.

2.7    /PERMANENT_DATABASE

       /PERMANENT_DATABASE (SET NODE only)

    Updates the node entries in the LAN volatile node database with
    any data currently set in the permanent database. This allows
    you to update the volatile database after changing data in the
    permanent database, rather than repeating the commands for each
    updated entry to apply the changes to the volatile database.

2.8    /ROOT

       /ROOT=directory-specification
       /NOROOT

    Supplies the directory specification to be associated with the
    file name. For cluster satellite service, the /ROOT qualifier
    specifies the satellite root directory. For noncluster service,
    this qualifier specifies the location of the file. If the file
    specification or the file name given in the boot request includes
    the directory name, this qualifier is ignored. The directory
    specification is limited to 127 characters.

    If you do not specify the /ROOT qualifier, the setting remains
    unchanged. The /NOROOT qualifier clears the field.

2.9    /SIZE

       /SIZE=value
       /NOSIZE

    Specifies the size in bytes of the file data portion of each
    downline load message. The default is the load data size
    specified for the device. The permitted range is 246 to 1482
    bytes. Use a larger size for better load performance and less
    server overhead.

    If you do not specify the /SIZE qualifier, the setting remains
    unchanged. The /NOSIZE qualifier clears the setting.

2.10    /V3

       /V3
       /NOV3

    Indicates that only MOP Version 3 formatted messages are to be
    used for downline load purposes, regardless of the requested
    format. This allows systems to load that have a problem with MOP
    Version 4 booting. This qualifier causes the requesting node to
    fail over from MOP Version 4 to MOP Version 3 when no response
    has been made to a MOP Version 4 load request.

    If you do not specify the /V3 qualifier, the setting remains
    unchanged. The /NOV3 qualifier clears the setting.

2.11    /VOLATILE_DATABASE

       /VOLATILE_DATABASE (DEFINE NODE only)

    Updates the node entries in the LAN permanent node database with
    any data currently set in the volatile database. This allows
    you to update the permanent database after changing data in the
    volatile database, rather than repeating the commands for each
    updated entry to apply the changes to the permanent database.

3  –  Examples

    1.LANCP> SET NODE VAXSYS/ADDRESS=08-00-2B-11-22-33 -
                            /FILE=APB.EXE -
                            /ROOT=$64$DIA14:<SYS10.> -
                            /BOOT_TYPE=ALPHA_SATELLITE

      This command sets up node VAXSYS for booting as an Alpha
      satellite into the cluster.

      The APB.EXE file is actually located on $64$DIA14:
      <SYS10.SYSCOMMON.SYSEXE>. Note that the <SYSCOMMON.SYSEXE> is
      supplied by the LANACP LAN Server process and is not included
      in the root definition.

    2.LANCP> SET NODE VAXSYS/ADDRESS=08-00-2B-11-22-33 -
                            /FILE=NISCS_LOAD.EXE -
                            /ROOT=$64$DIA14:<SYS10.> -
                            /BOOT_TYPE=VAX_SATELLITE

      This command sets up node VAXSYS for booting as a VAX satellite
      into the OpenVMS Cluster.

      The NISCS_LOAD.EXE file is actually located on $64$DIA14:
      <SYS10.SYSCOMMON.SYSLIB>. The <SYSCOMMON.SYSLIB> is supplied
      by the LANACP LAN Server process and is not included in the
      root definition.

    3.LANCP> SET NODE VAXSYS/ADDRESS=08-00-2B-11-22-33/NOROOT

      This command changes the LAN address associated with node
      VAXSYS and clears the current root specification.

    4.SET NODE CALPAL/ADDRESS=08-00-2B-11-22-33/FILE=APB_061.EXE

      This command sets up node CALPAL for booting an InfoServer
      image. It defines the file that should be loaded when a load
      request without file name is received from node CALPAL.

      Because the file does not include a directory specification,
      the logical name LAN$DLL defines where to locate the file. You
      could give directory specification using the file name or by
      using the /ROOT qualifier.

      Note that specifying the file name explicitly in the boot
      command overrides the file name specified in the node database
      entry.
Close Help