SNAX/APC Configuration and Management Manual

Introduction to SCF for SNAX/APC
SNAX/APC Configuration and Management Manual—138787
6-6
Object States
and the name of the partner LU itself. To illustrate, a PTNR-LU object might have the
name $APC1.LU01.CICSLU62, where $APC1 is the name of the PROCESS object,
LU01 is the name of the LU object, and CICSLU62 is the name of the PTNR-LU object
There are many other object types and object names used in SCF. The objects relevant
to this subsystem, and the hierarchical relationship that exists between SNAX/APC
objects, are described later in this manual.
Subordinate Objects
Some subsystems are structured hierarchically, with a group of objects of one type
logically subordinate to objects of another type. For example, multiple instances of a
transaction program can be running simultaneously. In this case, a TPN object (the
transaction program) has multiple TPI objects (the instances of the transaction program)
subordinate to it.
Some SCF commands support the SUB parameter that refers to all subordinate objects.
The SUB parameter has the following form:
SUB [ subtype ]
This parameter selects the subordinate objects affected by the command. The value of
subtype can be a subordinate object type or one of the keywords ONLY, ALL, or
NONE. If a subordinate object type is named, only objects of that type are affected.
ONLY specifies that only the subordinate objects are affected by the command. ALL
specifies that the named object and the subordinate objects are affected. NONE
specifies that only the named object and none of the subordinates is affected. If
subtype is omitted, ALL is assumed.
Object States
Objects can have operational states, such as STOPPED or STARTED. The exact
sequence of states an object goes through varies from object to object and from
subsystem to subsystem. Some subsystem commands recognize only a few states.
The operational state of an object at a given instant is important. For example, certain
commands have no effect on objects unless those objects are a specific state.
The following states are recognized by SCF for SNAX/APC:
Table 6-1. Object States
State Description
STARTED The object is initialized and ready for normal data traffic.
STARTING The object is being initialized and is attempting to start.
STOPPED The object is not ready for normal operations. STOPPED is equivalent to
down.
STOPPING The object is being stopped. The object is in the STOPPING state if its next
state is expected to be STOPPED.