OSI/MHS Configuration and Management Manual
Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-34
CLASS Objects
Examples of Commands for CLASS Objects
The following are examples of commands for CLASS objects.
The following example shows nonsensitive commands that you can use to obtain 
information about OSI/MHS classes and their subordinate objects:
INFO CLASS $ZMHS.#GI
INFO CLASS $ZMHS.#LO, DETAIL
INFO CLASS $ZMHS.#MS
INFO CLASS $ZMHS.#MS, DETAIL
NAMES CLASS $ZMHS.#RS, SUB ALL
START Changes the summary state of an OSI/MHS class from STOPPED to 
STARTED. 
You issue a START CLASS command as part of a normal startup, after 
you start the SUBSYS object and before you start the GROUP object. 
The transition from a STOPPED to a STARTED state is immediate: 
there is no STARTING state for a CLASS object.
You must start a class to start its subordinate groups. You can 
accomplish both with the START CLASS, SUB ALL command.
HP recommends that you use the SUB modifier. For example:
START CLASS $MHS1.#MR,SUB ALL
START CLASS $MHS1.#
∗
,SUB ALL
STATUS Displays the operational status of an OSI/MHS class.
STOP Changes the state of an OSI/MHS class from STARTED to STOPPED.
Before a CLASS object can be in the STOPPED state, the subordinate 
GROUP objects must be in the STOPPED state. You can achieve this 
effect with one command by including the option SUB ALL in the STOP 
command that is directed to the class. (See Caution on ABORT.)
The STOP command with the MAX option and the ABORT command 
have the same effect, except when you use the SUB ALL option. These 
commands apply to all subordinate groups, but the SUB ALL option has 
different implications, depending on the group.
Without the SUB ALL option, the STOP command is accepted only if the 
subordinate objects are in a STOPPED or STOPPING state. If the 
GROUP objects are stopping, then the CLASS objects will remain in a 
STOPPING state until all GROUP objects enter the STOPPED state.
When you specify SUB ALL, the modifiers FORCED and MAX are 
supported. The power modifier is applied to the subordinate objects, not 
the CLASS object. For more information about the FORCED and MAX 
modifiers, see GROUP Objects on page 2-48.










