SNAX/HLS Management Programming Manual

Objects
Elements of SPI Messages for SNAX/HLS
4–6 104708 Tandem Computers Incorporated
Object Summary States SNAX/HLS reports a summary state for each object it manages. Summary states of
SESSION objects reflect a summary of SNA states. The summary state of the
SNAX/HLS process is artificially reported as STARTED.
The five summary states for SESSION objects are:
DEFINED
STARTED
STARTING
STOPPING
SUSPENDED
DEFINED Summary State
This summary state indicates that a session has been defined but has not yet begun. In
terms of application activities, this summary state indicates that the HLS–ALLOCATE
verb has been issued but the HLS–OPEN verb has not. This condition also arises after
a session has been terminated (either by the owning application or by SNA protocol
events) but before it has been deallocated.
By issuing an OPEN–SESSION or HLS–OPEN verb, an application program causes a
session to enter the STARTING summary state. When a session is deallocated as the
result of a CLOSE–SESSION or HLS–DEALLOCATE verb, the session is deleted. The
ABORT SESSION command also deletes a session.
STARTED Summary State
This summary state indicates that a session is active. The detailed session status
contained in the response to the STATUS SESSION command should be examined for
further details.
STARTING Summary State
This summary state indicates that a session has been allocated and that protocol
activities have been initiated to begin data traffic. Specifically, an application program
has issued the HLS–OPEN verb (or the OPEN–SESSION verb), and the session–
initiation activities are still in progress.
In SNA terms, this summary state indicates that the session cannot send data traffic.
The BIND, STSN, and SDT messages (when relevant) are yet to be communicated.
If the session startup succeeds, the session enters the STARTED summary state. If the
startup fails, either the session enters the DEFINED summary state or the session is
deleted, depending upon how the application program allocated the session.
STOPPING Summary State
This summary state indicates that a session is terminating. In SNA terms, it means the
SHUTD request has been communicated and the UNBIND request is expected to
follow.