LANCP, DEFINE, NODE
*Conan The Librarian
Enters a node into the LAN permanent node database or modifies an
existing entry. Requires SYSPRV privilege.
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.
DEFINE NODE 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
1.LANCP> DEFINE NODE GALAXY/ADDRESS=08-00-2B-11-22-33 -
This command sets up node GALAXY in the LAN permanent node
database for booting as a VAX satellite into an OpenVMS
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
2.LANCP> DEFINE NODE ZAPNOT/ADDRESS=08-00-2B-11-22-33 -
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 -
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