OSI/FTAM Configuration and Management Manual

FTAM Management Environment
OSI/FTAM Configuration and Management Manual—421944-001
2-15
PROCESS Objects
PROCESS Object States
A PROCESS object has four states—STARTED, STOPPED, SUSPENDED, and
UNDEFINED—and four intermediate states—STARTING, ABORTING, STOPPING,
and SUSPENDING. Table 2-5
describes the states and intermediate states of the
PROCESS object.
When a process is in an intermediate state (ABORTING, STOPPING, STARTING, or
SUSPENDING), requests that are pending for that process are rejected and an error
message is returned.
Table 2-5. Process and Intermediate States
Process State Description of Process Condition
ABORTING The process is in transition to the STOPPED state because the
ABORT command has been received. The process is running
but cannot accept new user requests.
STARTED The process is running and can accept user requests. When the
APLMGR process is in the STARTED state, the MIB is open.
STARTING The process is in transition to the STARTED state because a
START command was issued to it when it was stopped or
suspended. User requests are not accepted until the process is
started.
STOPPED The process is defined in the MIB, but it is not running. When
the APLMGR process places a process in the STOPPED state,
the operating system views the process as nonexistent; the MIB
is closed.
STOPPING The process is in transition to the STOPPED state because the
STOP command has been received. The process is running but
cannot receive new user requests.
SUSPENDED The process is running but cannot accept user requests. If the
APLMGR process is in the SUSPENDED state, it cannot
communicate with other OSI processes, and the MIB is closed.
SUSPENDING The process is in transition to the SUSPENDED state because
the SUSPEND command has been received. The process is
running but cannot accept new user requests.
UNDEFINED The process state cannot be determined because of an error.