PAM Configuration and Management Manual

SCF for PAM
PAM Configuration and Management Manual—523349-003
3-5
SCF Object States
The PORT and the MSAP are on the same level but differ in the method with which
clients access them. Clients that use the file system access the PORT, but clients that
use the message system access the MSAP. SNAX over token ring is the only
supported message-system client.
The PORT and MSAP are related because PAM dynamically creates an LLC2-type
PORT when SNAX sends an Open SAP request through the MSAP. Although the
LLC2 port could be considered subordinate in function to MSAP.#SNATR, the LLC2
port was implemented under the PORT hierarchy because it has attributes similar to
the PORT and some SCF commands could operate on it.
The SESSION object is subordinate to the LLC2 PORT. The SESSION object provides
SNAX with the ability to run multiple communications sessions on a single LLC2 port.
You can run up to 255 sessions per LLC2 port.
SCF Object States
SCF objects can be in different states of operation, depending on the SCF command
issued to that object or the state of the underlying, associated LIF. The operational
states are:
Table 3-3 lists the possible operational states for the SCF objects in PAM.
STARTED
The object is running and is ready to accept requests from other
subsystem components or applications. This state results from the
START command for most objects.
STARTING
The object is on its way to the STARTED state because a
command was issued to start it.
STOPPED
The object does not accept requests from other subsystem
components and applications. This state results from the STOP
command.
STOPPING
The object is on its way to the STOPPED state because a
command was issued to stop it.
SUSPENDED
The kind of information allowed to flow to and from the object is
restricted. Typically, data flow is prevented.
Table 3-3. Possible Operational States for PAM Objects (page 1 of 2)
Object
Possible States
STOPPING STOPPED STARTING STARTED SUSPENDED
LINE X X X X X
MSAP X X X X