OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-70
SUBSYS (Subsystem) Objects
STARTED, for an OSI/MHS subsystem, is the state that allows you to start the
subsystem subordinate objects. This state results from directing a START command to
the SUBSYS object. The SUBSYS object is the first object you start in an OSI/MHS
subsystem. Before you start this object, you should know the specific SUBSYS
attributes you want to use.
The STOPPED state means that the OSI/MHS subsystem and all its subordinate
classes and groups have been stopped. (It is not necessary for APPL objects to be in
the STOPPED state; APPL objects can always remain in the STARTED state.) To
accomplish this, you first stop the subordinate objects, then stop the SUBSYS object.
The SUBSYS object must in the STOPPED state before you can alter its attributes.
STOPPING is a transitional state. It means that a STOP command was directed at the
subsystem, but the subordinate classes are stopping first.
UNDEFINED means that no subsystem with the specified name is defined to the MHS
manager. If you try an SCF operation on an UNDEFINED (nonexistent) subsystem,
SCF returns the following error message:
object name not found
Naming SUBSYS Objects
A SUBSYS object name has the form:
system
is the name of the system (node) that runs the MHS manager process for this
OSI/MHS subsystem.
Figure 2-8. SUBSYS Object Summary States
[\system.]$manager-process.#subsystem
UNDEFINED STOPPED STARTED
ADD
DELETE
START
STOP
or ABORT
STOPPING
T 022VS .VSD
Note: Boxes represent the stable subsystem states; ovals represent
transition states; and arrows represent the SCF commands that change the
state of the subsystem.