APN Configuration and Management Manual

Objects for SNAX/XF and SNAX/APN

SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006

12-9

Object States

A PU object can be in one of five states: ABORTING, STARTED, STARTING,

STOPPED, or STOPPING. These object states are described later in this section.

SESSION Objects

For SNAX/XF and SNAX/APN, a SESSION object is a non-configured object. A

session refers to a temporary logical connection between two SNA components. The

only types of sessions supported by SNAX/XF and SNAX/APN are sessions between

two LUs (LU-LU sessions). Thus, when LUs are communicating with each other, they

are said to be in session.

A SESSION object allows you to get information about a particular session or to

terminate a session without affecting the associated LU.

When SNAX/APN is used with SNAX/APC for Advanced Peer-to-Peer Communication

(APPC), it supports multiple and parallel sessions. In this case, a single LU object can

have several SESSION objects subordinate to it. Each of these SESSION objects is

identified by a 16-digit hexadecimal fully qualified procedure correlation identifier

(FQPCID), which is included in the SESSION object name.

Naming Conventions

For SNAX/XF, the SESSION object name is defined to be the same as the LU object

name over which the session is carried. Consequently, the format of SESSION object

names is the same as for LUs; there is no separate object name for a SESSION

object.

For SNAX/APN, a SESSION object name has the following format:

line

is the name of the associated line. The line name consists of 1 through 7

alphanumeric characters, the first of which must be a letter.

subdevice

is the subdevice name of the associated LU object. The subdevice name consists

of 1 through 7 alphanumeric characters, the first of which must be a letter.

nnnnnnnnnnnnnnn

is the 16-digit hexadecimal fully qualified procedure correlation identifier (FQPCID).

For example, the following is a valid SESSION object name:

$APN1.#LU1.D95F195317EA7101

$line.#subdevice.nnnnnnnnnnnnnnnn