OSI/MHS SCF Reference Manual

OSI/MHS SCF Commands
OSI /MHS SCF Reference Manual—424828-001
2-60
ADD GROUP Command
MR-TRANSMIT-MODE
specifies the mode of operation of an MR group. This value can be DRAIN or
NORMAL. The default value is NORMAL.
DRAIN means that an MR group continues to transmit to local or remote recipients
messages it is currently processing, but that it does not accept any incoming
messages from any source. That is, the MR group refuses incoming associations or
message transfers from remote MTAs and all local message submissions from MS
APPL objects and GATEWAY objects. Eventually, an MR group operating in
DRAIN mode is emptied of all its messages; it reaches an idle state.
NORMAL means that an MR group is capable of both sending and receiving
messages. This is the usual mode of operation for an MR group
Typically, DRAIN mode is used to empty the messages from an MR group prior to
deletion of that MR group. In this context, an MR group operating in NORMAL
mode is stopped, altered such that it is in DRAIN mode, and then restarted. When
the MR group is empty of messages, it can be stopped and deleted.
The STATUS PROCESS and STATUS ENTRY commands are used to determine
that an MR group has no more messages to process. First, enter a STATUS
PROCESS command for the group’s MRP. Then, enter the command:
STATUS ENTRY #*
If the Active-MTAs and Active-APPLs fields in the STATUS PROCESS MRP
display are both zero, and if there are no items returned in any STATUS ENTRY
display with the Group-Name field set to the group’s object name, then there are no
more messages left for the MR group to process.
Once all messages have been processed by the MR GROUP object, check that all
messages have been processed by the gateways (both normal or P1 user exit) before
deleting the PDU store. The PDUDIAG command STATUS GROUP will display all
PDUs in a group's PDU store. PDUs that have not been processed by the gateway
will have a state of “DELIV-GW” or “P1-EXIT.”
MRP-BACKUP
specifies the backup CPU in which the MRP is to run. This attribute is optional; if
you omit it, the backup CPU for the group is assumed. No range checking is done;
however, the maximum value of cpu-number should not exceed the number of
CPUs on the target system minus one (for example, 0 to 7 on an eight-CPU system).
MRP-CPU
specifies the CPU in which the MRP is to run. This attribute is optional; if you omit
it, the default CPU for the group is assumed. No range checking is done; however,
the maximum value of cpu-number should not exceed the number of CPUs on
the target system minus one (for example, 0 to 7 on an eight-CPU system).