OSI/MHS Management Programming Manual

Commands and Responses
OSI/MHS Management Programming Manual—424824-001
5-74
ADD GROUP
Tokens in Command Buffer
ZSPI-TKN-MANAGER
is the MHS manager name, that is, the process to which SCP is to send this
command. This token is required and must occur only once.
ZCOM-TKN-OBJNAME
is the name of the GROUP object to be added. This token is required.
ZMHS-MAP-GROUP
is an extensible structured token that contains attributes common to all groups. This
token is required. The ZMHS-MAP-GROUP definition, ZMHS-DDL-GROUP,
contains the following fields:
ZPRIM-CPU
is the default CPU in which to run processes in this group. No range checking is
performed. However, this value should not exceed the number of CPUs on the
target system minus one (for example, a value in the range 0 to 7 for an eight-
CPU system). The SPI-NULL value for this field is 255.
ZSEC-CPU
is the default secondary CPU for this group. No range checking is performed.
However, this value should not exceed the number of CPUs on the target system
minus one (for example, a value in the range 0 to 7 for an 8-CPU system). The
SPI-NULL value for this field is 255.
ZPRI
is the default priority at which to run processes in this group. The priority must
be less than the MHS manager priority. The SPI-NULL value for this field is
255.
ZPDU-FNAME
is the PDU store where processes in the group write messages. Processes access
other PDU stores for purposes other than writing messages. A PDU file can be
associated with only one group. If a PDU file is specified that is already
associated with another group, an error is returned. The PDU store file must be
on the same node as the MHS manager. The SPI-NULL value for this field is 0.
ZPDU-LOG-FNAME
is the PDU store where processes in the group write logs. Processes access
other PDU log stores for purposes other than writing messages. A PDU log file
can be associated with only one group. If a PDU log file is specified that is
already associated with another group, an error is returned. The PDU log file
must be on the same node as the MHS manager. The SPI-NULL value for this
field is 0.