SNAX/XF and SNAX/APN Configuration and Management Manual

Objects for SNAX/XF and SNAX/APN
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
12-7
Naming Conventions
The PROCESS object is provided because the BOOT, PRIMARY, and SWITCH
commands apply to the line-handler process (PROCESS) and not to the logical line
(LINE). PROCESS objects do not appear in SCF displays as part of the object
hierarchy.
Naming Conventions
The PROCESS object name must match the name of a line-handler process defined
through the SCF ADD DEVICE command. The PROCESS name syntax is as follows:
line-handler-name
is the name of a line-handler process. It can contain from 1 through 7
alphanumeric characters, the first of which must be a letter.
For example, the following are valid PROCESS object names:
$SNA1
$APNA
Object States
A PROCESS object is always in the STARTED state. This state is described later in
this section.
PU Objects
A PU object refers to an SNA physical unit—sometimes the local PU (on the NonStop
node) and sometimes a remote PU (on another node).
SNAX/XF PU Objects
SNAX/XF PU objects can be subordinate either to a LINE object or the SUBSYS
object. If the latter, they are called switched floating PU objects. When a switched
floating PU serves a dial connection, the PU is subordinate to the dial line.
SNAX/APN PU Objects
SNAX/APN PU objects are always subordinate to a LINE object. SNAX/APN requires
that two classes of PU objects be subordinate to a line: a local PU object, which
represents the control point on the NonStop system, and remote PU objects, which
represent external resources. Thus, there is a local PU object to which local LU objects
are subordinate and remote PU objects to which remote LU objects are subordinate.
$line-handler-name