OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-54
GROUP Objects
Examples of Commands for GROUP Objects
The following are examples of commands for GROUP objects.
The following examples show nonsensitive commands you can use to obtain
information about OSI/MHS groups and their subordinate processes:
INFO GROUP $ZMHS.#GI.GIGROUP
∗
INFO GROUP $ZMHS.#LO.LOGROUP3, DETAIL
INFO GROUP $ZMHS.#MS.MSGROUP
∗
INFO GROUP $ZMHS.#MS.MSGROUP3, DETAIL
NAMES GROUP $ZMHS.#MR.MRGROUP2
STATUS GROUP $ZMHS.#RS.RSGROUP
∗
, SEL STARTED
Most attributes of a group actually refer to the PROCESS objects it contains. Some of
the attributes apply to a particular kind of group or process (MR, MS, or RS); some
apply to any of the three kinds.
For example, the attribute MS-PNAME gives a name to the MS process that is created
when you add an MS group. The attributes CPU and BACKUP determine on which
CPU the primary process and its backup will run. The processes do not run as
NonStop process pairs; the MHSMGR starts a process in the backup CPU if a primary
CPU fails. The following example shows an MS process named $MHS1.#I11, running
on CPU 2 with a backup on CPU 3:
ASSUME GROUP $MHS1.#MS
ADD .MSGROUP3, &
CPU 2, &
BACKUP 3, &
STOP Changes the state of an OSI/MHS group from STARTED to STOPPED.
Before the GROUP object can be in the STOPPED state, the
subordinate PROCESS object(s) must stop. The STOP command does
this automatically, and, during the time this takes, the group is in the
STOPPING state. This occurs differently depending on whether you
use the MAX option or the FORCED option. The FORCED option is the
default.
When you issue STOP with the FORCED option, the MHS manager
process terminates the group associations and subordinate process(es)
in an orderly way and stores the group message queue on disk. The
current message transfer operation will be completed whenever the
group is restarted.
When you issue a STOP command with the MAX option, the MHS
manager process aborts the group associations, stops its subordinate
process(es) abruptly, and does not save its message queue. This
action has the same effect as the ABORT command.
Note. Without the MAX option, stopping groups takes longer than aborting them, but restart
and recovery take less time.