1  DEFINE
 

2  DEVICE
   Enters a device into the LAN permanent device database or
   modifies an existing entry. Requires SYSPRV privilege.

                               QUALIFIERS

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

   Format

     DEFINE DEVICE  device-name
 

3  Parameter
 

device-name

   Supplies the name of a device to be added to the LAN permanent
   device database or an entry to be modified. The device name has
   the form ddcu where dd is the device code, c is the controller
   designation, and u is the unit number. LAN devices are specified
   as the name of the template device, which is unit 0; for example,
   the first PCI Ethernet device is specified as EWA0, the second as
   EWB0.
 

3  Examples

   1.LANCP> DEFINE DEVICE EXA0/MOPDLL=(ENABLE,EXCLUSIVE)

     This command defines LAN device EXA0 to enable LANACP MOP
     downline load service in exclusive mode. The setting of the
     KNOWNCLIENTSONLY and SIZE characteristics are not changed. If
     the device entry does not currently exist in the LAN permanent
     device database, these settings are set to the defaults.

   2.LANCP> DEFINE DEVICE/ALL/MOPDLL=NOEXCLUSIVE

     This command sets all LAN devices defined in the LAN permanent
     device database to nonexclusive mode for LANACP MOP downline
     load service.

   3.LANCP> DEFINE DEVICE/ALL/UPDATE/VOLATILE_DATABASE

     This command enters all Ethernet devices into the LAN permanent
     device database and updates the entry to include the current
     parameter values.
 

2  NODE
   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
 

3  Parameter
 

node-name

   Supplies the name of a node to be added to the LAN permanent 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.
 

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