VMS Help LANCP, DEFINE, NODE, Examples  *Conan The Librarian (sorry for the slow response - running on an old VAX)

    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 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.

    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 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.

    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 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.