Expand Configuration and Management Manual (G06.24+)

Subsystem Control Facility (SCF) Commands
Expand Configuration and Management Manual—523347-008
15-4
Object States
The following are some typical device names:
PROCESS Object
The PROCESS object type may refer to the Expand manager process ($ZEXP), the
network control process ($NCP), or an Expand line-handler process.
ENTRY Object
The ENTRY object type identifies an entry in the network routing table (NRT). You use
the ENTRY object to delete a system name from the NRT if the system associated with
that name is not connected to the network. The ENTRY object type applies only to the
object name $NCP.
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.
Applicable states are discussed with each subsystem description.
The operational state of an object at a given instant is important. For example, certain
commands have no effect on objects when those objects are in a particular state but
can affect the object when it is in another state.
The following states are recognized by the Expand subsystem:
$SYS1 An Expand line-handler process that manages a
single line to the node named \SYS1
$PATH A path logical device
$LINE1, $LINE2, and so on Line logical devices
State Description
ABORTING The object is being aborted. Typically, this state is triggered by an ABORT
command or by a device malfunction. In this state, no new links are
allowed and drastic measures are applied to reach the STOPPED state.
This state is irrevocable.
DIAGNOSING This state is entered when the object is being diagnosed by a diagnostic
process.
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, not ready, or killed.