OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-58
null Objects
Examples of Commands for the MON Object
The following are examples of commands for the MON object.
The first several examples illustrate the nonsensitive commands you can use to obtain
information about the MHS manager process:
INFO MON $ZMHS
INFO MON $ZMHS, DETAIL
LISTOPENS MON $ZMHS
STATS MON $ZMHS
STATUS MON $ZMHS
STATUS MON $ZMHS, DETAIL
The next two examples show sensitive commands you can use to manipulate the MHS
manager process:
STATS MON $ZMHS, RESET
PRIMARY MON $ZMHS, 5
This STATS command differs from the earlier, nonsensitive example because it resets
the statistics counters. This PRIMARY command switches the primary MHS manager
process to CPU 5. The two commands do not directly affect other objects.
The next example tells the MHS manager process to generate trace files. When the
file is full, it will wrap around and write the next record at the beginning of the file, over
the first record.
TRACE MON $ZMHS, SELECT ALL, WRAP, TO $DATA.MHS.TRACE
The final example shows how to specify an EMS alternate collector for OSI/MHS
accounting messages. (The commands are the same whether such messages were
earlier ignored or sent to a different collector.) Before you could issue such a
command, you would have to do two things:
•
Configure and start an alternate collector (through SCF or TACL), giving it a
process name:
EMSACOLL/name $ALT,nowait,cpu 1/backup 0
•
Stop the SUBSYS object (which implies stopping any subordinate CLASS objects
first).
Here is the required sequence of OSI/MHS commands (except those needed to stop
subordinate classes, if any). This example assumes an alternate collector name of
$ALT:
STOP SUBSYS $ZMHS.#SUBS1
ALTER MON $ZMHS, COLLECTOR-1 $ALT
null Objects
There can be only one instance of the null object type in a subsystem. In an OSI/MHS
subsystem, this instance is automatically defined when the MHS manager process is