SNAX/APC Management Programming Manual

Object Summary States
Elements of SPI Messages for SNAX/APC
3–14 111813 Tandem Computers Incorporated
Object Summary
States
Objects defined for SNAX/APC are always in one of several states. The state of an
object at any given instant is important: certain commands require that an object be in
a particular state. For most objects, the state changes as commands are issued against
the object. This can be illustrated by the act of starting an LU, which causes the state to
change from STOPPED, to STARTING, to STARTED.
The state is used in several ways. For example, when the SNAX/APC subsystem
responds to a STATUS command, it always returns the state of the object. When the
SEL-SUMSTATE modifier is used in a command, it indicates that the command
applies only to objects in the specified state. Additionally, the state must be valid for
the specified object type or command. For example, if the STATISTICS command is
applied to the LU object type, the only valid values for SEL-SUMSTATE are STOPPED,
STARTED, and STARTING.
Table 3-1 summarizes the object states as they apply to the various object types.
Table 3-1. Object Summary States
Object
Summary State CONVERSATION LU PROC PTNR-LU PTNR-MODE SESS TPN TPI
STOPPED X * XX X
STOPPING X * XX
STARTED X X X X X X X X
STARTING X X * XXXXX
*The summary state for the PROCESS object is STARTED. A backup process can have additional operating system process states,
such as STARTED, STARTING, STOPPED, STOPPING, and SUSPENDED. Refer to the SPI Common Extensions Manual for more
information on backup processes and object summary states.