OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-55
MON (Monitor) Objects
PRI 130, &
PDU-STORE MHS1MS1.PDUMS1, &
PDU-LOG-FILE MHS1MS1.LOGMS1, &
WORK-SV MHS1MS1, &
MS-PNAME $MHS1.#I11, &
MSG-STORE-SV MHS1MS1, &
MR-COUNT SYS
Note that the MS process name used, $MHS1.#I11, includes the name of the MHS
manager process, but omits system, class, and group names. This form of the process
name is required by the attribute MS-PNAME and has nothing to do with the preceding
ASSUME command. MS-PNAME, like all other attributes, is unaffected by the
ASSUME command.
MON (Monitor) Objects
There can be only one instance of the MON object type in an OSI/MHS subsystem.
The MON object represents the MHS manager process, the first OSI/MHS process
created during installation. Implicitly, the MHS manager process receives, interprets,
and carries out all SCF commands directed to the subsystem—both the commands
that create other OSI/MHS objects and the commands that control them.
Using commands that specify the MON object, you can:
•
Switch the primary and backup processes of an MHS manager
•
Find out the attribute values and operational status of an MHS manager process
•
Obtain trace records from an MHS manager process, statistics about its
performance, and information about the other processes that have opened it
•
Stop an MHS manager process and alter its attributes
MON Object States
In an OSI/MHS subsystem, the MON object represents the MHS manager process.
The manager process is a NonStop process pair; it is the only NonStop process pair in
the subsystem. The STATUS command for the MON object displays the states of the
primary and backup manager processes. When the MHS process is running, the MON
object is in the STARTED state.
The STARTED state means that the MHS manager is running, ready to receive
commands and to direct the subsystem. The STARTED state results from running the
MHS manager.
You must start the MHS manager process pair before you can configure and start the
other components of an OSI/MHS subsystem.
The STOPPED state means that a STOP or ABORT command was directed at the
MON object. As a result, the MHS manager process has stopped and cannot accept
further commands.