OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-51
GROUP Objects
class
is the name of the CLASS object that includes this OSI/MHS group.
The class name must be one of the following:
GI (in a gateway interface group name)
LO (in a local service group name)
MR (in a message relay group name)
MS (in a message store group name)
RS (in a remote operations service group name)
gsystem
is the name of the system on which you install this OSI/MHS group. gsystem
should be the same system where the MHS manager resides.
group
is the name used to distinguish this GROUP object from all other objects in this
OSI/MHS subsystem, and in particular from other GROUP objects. This name
must be a letter followed by 0 through 15 alphanumeric characters.
For example, if your MHS manager process is named $ZMHS and runs on the system
where you want to add a message store group, you could name the group
$ZMHS.#MS.MSGROUP1. You specify the group name in the ADD command for the
GROUP object.
Wild-Card Characters in Names for GROUP Objects
The name of a GROUP object does not have to be fully qualified or complete: you can
substitute a wild-card character for one or more lower level qualifiers or characters. A
command that includes an object name with a wild card affects every object whose
name fits the incomplete pattern.
In particular, if you want to issue a GROUP command that applies to all the groups in a
class, you can replace the group qualifier with an asterisk:
$ZMHS.#MS.
∗
or $ZMHS.#MS
∗
GROUP objects have some common attributes (such as priority, PDU store, and
backup); therefore, wild-card characters are useful for commands such as:
ALTER GROUP $ZMHS.#M
∗
.
∗