IPX/SPX Configuration and Management Manual

Managing NonStop™ IPX/SPX With the Subsystem
Control Facility (SCF)
IPX/SPX Configuration and Management Manual—425731-001
3-5
Summary States
State Transition Diagram
The valid summary states for the PROCESS object are ABORTING, STARTED,
STARTING, STOPPED, and STOPPING. Figure 3-3 shows the state-transition diagram
for the PROCESS object.
Once defined, the process enters the STOPPED state, in which the process is quiescent
and nonoperational (use the START command to make the PROCESS object fully
operational). The startup sequence may not complete successfully if a resource is
configured incorrectly or is otherwise unavailable. The STOPPED state is unique
because it has a DIAGNOSTIC substate associated with it. This substate indicates the
reason the process is STOPPED. The reason is either normal, memory, or network.
•
The normal substate indicates that the process became STOPPED by an operator
issuing the STOP command.
•
The memory substate indicates that the process did not complete its initialization
because of a lack of QIO memory.
•
The network substate indicates that the process did not complete its initialization
because of a network problem such as a bad LAN adapter, missing LAN cable, or
the NetWare server not being up or reachable.
The STOPPING, STARTING, and ABORTING states are intermediate states that the
process can enter when it is in between the STARTED and STOPPED states. From the
STOPPED state, a START command changes the state to STARTING, then to
STARTED. From the STARTED state, a STOP or ABORT command changes the state
to STOPPING or ABORTING, then to STOPPED or ABORTED, as appropriate.
Figure 3-3. PROCESS Object: State-Transition Diagram
016CDT .CDD
DELETE ADD
ALTER, INFO,
......
STOP
STARTED
INFO, LISTOPENS,
.......
STARTING
START
Startup
Successful
ABORTINGSTOPPING
ABORT
Stop Processing
Completed
Startup
Failed
STOPPED
Abort
Completed