OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-56
MON (Monitor) Objects
Naming MON Objects
For any OSI/MHS subsystem, the MON object name is the name given the MHS
manager process. The same name is used for the null object. This name has the
form:
system
is the name of the system (node) that runs the MHS manager process for this
OSI/MHS subsystem.
manager-process
is the process name of the MHS manager process. This name must be a letter
followed by zero through three alphanumeric characters.
The manager process name is shared by all objects in the subsystem, but for all
except MON and null, it is qualified by one or more additional (lower level) names.
For example, you could name the MHS manager \SYSTEM1.$ZMHS when you install
it. Then you would use the name “$ZMHS” in commands directed to the MON object
from inside SYSTEM1.
SCF Commands for the MON Object
You can direct any of the following SCF commands to the OSI/MHS MON object
specified or assumed in the command. You do not have to start the MON object
because this occurs when you run the MHS manager. For information about how to
run the MHS manager, see Section 6, Starting, Stopping, and Updating Your OSI/MHS
Subsystem.
[\system.]$manager-process
ABORT Changes the state of the MHS manager process pair from STARTED
to STOPPED.
Since the MON object has no subordinate objects of its own, the
ABORT and the STOP commands have the same effect.
Caution. It is rarely necessary to abort the MHS manager process. If it becomes necessary to
do so, you must first stop all the CLASS objects subordinate to the SUBSYS object, then the
SUBSYS object, and only then the MON object.
Aborting the MON object without these precautions does not stop the subsystem, but it does
make it incapable of receiving SCF commands and leave it vulnerable to unrecoverable errors.
Therefore, you should never stop or abort the MON object when the system is running or when
the SUBSYS object is not in the STOPPED state. All SUBSYS, CLASS, and GROUP objects
must be in a STOPPED state before you abort or stop the MON object.