OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-35
CUG (Closed User Group) Objects
NAMES CLASS $ZMHS.#MR, SUB ONLY
STATUS CLASS $ZMHS.#RS, SUB ALL, SEL STARTED
The MS CLASS object has only one attribute: namely, the maximum number of
mailboxes in the message store of each MS group. The number of APPL objects you
create for any MS group must not exceed the number of mailboxes you allow for the
MS class.
The maximum number of mailboxes in the PDU store of any MS group is set by the
ADD command that creates the MS class. If you do not include the mailbox attribute in
the command, the default maximum is 100. To specify a smaller maximum, include the
attribute:
ASSUME CLASS $ZMHS
ADD #MS, NUMBER-OF-MAILBOXES 50
START #MS
You may decide later that 50 mailboxes (users) per MS group are not enough (or too
many). Then, if the ASSUME command is no longer in effect, you could enter:
STOP CLASS $ZMHS.#MS
ALTER CLASS $ZMHS.#MS, NUMBER-OF-MAILBOXES 80
START CLASS $ZMHS.#MS
CUG (Closed User Group) Objects
The CUG object type defines a closed user group within the OSI/MHS subsystem. A
CUG defines a set of users who may exchange messages only with one another. If
CUG checking is enabled, then all message and probe transfers must be within locally
defined CUGs. If OSI/MHS detects a CUG violation, a non-delivery notification will be
sent for each invalid recipient.
In addition to specifying which users can communicate with one another, a CUG can
place any of the following restrictions on the messages exchanged:
•
Permissible content types
•
Maximum message size
•
Minimum X.400 message priority
CUG Object States
A CUG object has a summary state of DEFINED only.
Naming CUG Objects
A CUG object name has the following form:
[\system.]$manager-process.#cug