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-8
Naming Conventions
Local PU Object
You cannot use SCF to define a local PU object. A PU object, named #ZNT21, is
automatically added for SNAX/APN lines. Although you cannot use SCF to add or
alter this PU object, you can issue a STOP or ABORT command to stop it and then
restart it with a START command. You can also issue INFO PU, STATS PU, and
STATUS PU commands to inquire about it (for example, INFO PU $L1.#ZNT21) and to
reset its statistics counters. This PU object on the NonStop system also appears in the
NAMES display.
Note that if a NonStop system has more than one line that uses SNAX/APN, the local
PU for each of these lines will be #ZNT21. That is, all local LUs are subordinate to a
local PU named #ZNT21.
Remote PU Object
On every line that uses SNAX/APN, at least one remote PU object must be configured
through SCF. This remote PU represents the adjacent type 2.1 node, and for point-to-
point connections, you can only configure one to a line; a NonStop node regards all
LUs with which it communicates as residing on an adjacent node, no matter how
dispersed they might be throughout a network. For multipoint configurations in which
the NonStop node serves as the primary link station, you must define a remote PU for
every physical node with which that NonStop node will communicate.
Naming Conventions
PU object names have the following format:
line
is the name of the associated line. The line name consists of from 1 through 7
alphanumeric characters, the first of which must be a letter.
subdevice
is a subdevice name identifying the PU object. The name consists of 1 through 7
alphanumeric characters, the first of which must be a letter.
For example, the following are valid PU object names:
$SNAP1.#PU1 (permanently subordinated PU
object)
$SSCP.#PU1 (switched floating PU object)
$APN1.#PU1
{ $line.#subdevice }
{ $SSCP.#subdevice }