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.