Enters a node into the LAN permanent node database or modifies an
    existing entry.

    Requires SYSPRV privilege.

                                QUALIFIERS

       See the SET NODE command for a list of qualifiers and the
       description of each. Except where noted, the only difference
       is that DEFINE NODE applies to entries in the LAN permanent
       node database rather than the volatile node database.

    Format

      DEFINE NODE node-name

1  –  Parameter

 node-name

    Specifies the node name in the LAN permanent node database.

    When entering a new node, you can use the system node name recorded in
    the system parameter SCSNODE, or another name limited to 63 characters
    in length.

2  –  Examples

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

      This command sets up node GALAXY in the LAN permanent node database
      for booting as a VAX satellite into an OpenVMS Cluster.

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

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

      This command sets up node ZAPNOT for booting as an Alpha satellite
      into an OpenVMS Cluster.

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

    3 LANCP> DEFINE 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 a
      file name is received from node CALPAL.

      Because the file does not include a directory specification, the
      logical name LAN$DLL defines the location. You can include the
      directory specification in 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.