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-6
Object States
However, if LUs on a NOnStop system are to initiate sessions with LUs in an adjacent
node or network, remote LU objects must be explicitly defined. A remote LU object is
created when the name of a remote PU is specified in the PUNAME attribute.
When you use XLF for remote device logon, you can configure a remote LU object to
represent the HP NonStop Logon Manager (ILOGMGR) for IBM systems. However,
you need not do so. If the DYNAMIC attribute of the remote PU object is specified as
ON, a remote LU object representing the ILOGMGR is dynamically added when the
ILOGMGR sends a BIND request. When the ILOGMGR LU object is dynamically
added, the ILOGMGR initiates all sessions with the TLOGMGR.
You can run multiple ILOGMGRs on a remote IBM system. When you do so, you
configure a separate ILOGMGR LU object for each one, or, if the DYNAMIC attribute
for the PU is set to ON, a separate ILOGMGR LU is created automatically for each one
that has not been predefined.
If you are using the device acquire feature, you must configure a remote LU object for
every device the application on the NonStop system is to acquire. In this manual, these
LU objects are called acquired remote LU objects. These are the LU objects that the
application on the NonStop system opens. Acquired remote LU objects cannot be
added dynamically.Naming Conventions
LU 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 LU object. The name consists of 1 through 7
alphanumeric characters, the first of which must be a letter.
For example, the following are valid LU object names:
$SNAP1.#LU1 (permanently subordinated LU)
$SSCP.#LU1 (switched floating LU)
$APN1.#LU1
Object States
An LU object can be in one of three states: ABORTING, STARTED, or STOPPED.
These object states are described later in this section.
PROCESS Objects
PROCESS object names are used to refer to line-handler processes.
{ $line.#subdevice }
{ $SSCP.#subdevice }