OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-52
GROUP Objects
SCF Commands for GROUP Objects
You can direct any of the following SCF commands to the OSI/MHS GROUP object
specified or assumed in the command:
ABORT Forces the state of an OSI/MHS group from STARTED to STOPPED.
Before the GROUP object can be in the STOPPED state, its
subordinate PROCESS object(s) must stop. The ABORT command
does this automatically, and during the time this takes, the group is in
the STOPPING state.
When you issue an ABORT command, the MHS manager process
aborts the group’s associations, stops its subordinate process(es)
abruptly, and does not save its message queue. This has the same
effect as a STOP command that includes the MAX option.
Note. Aborting groups is faster than stopping them (without the MAX option), but restart and
recovery take longer after an ABORT command.
ADD Creates a group that has the name and attributes specified in the
command, then adds the name and attributes to the OSI/MHS
configuration database. Most of the attributes refer to the process(es) in
the group.
Before you add a GROUP object, you must add the class to which it
belongs. After you add the group, you still have to start it in order to
start its subordinate process(es).
You must add at least one MR group before you add the first MS group.
The ADD command for an MS GROUP object allows you to specify
whether or not MS bind authentication parameters are to be validated
using an external password server process. If so, you also specify the
name of the password server. For more information on password
servers, see OSI/MHS Security Interfaces on page 2-11. For
information on integrating a password server, see the OSI/MHS
Management Programming Manual.