OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-48
GROUP Objects
This example shows the GATEWAY object name is $ZMHS.#GW1, and it is associated
with two entry manager processes: $EM01 and $EM02. This gateway is a 1984
implementation. In this example, the OSI/MHS subsystem will validate each message
before transferring it to the gateway, and it will respond to probes destined for the
gateway. The OSI/MHS subsystem responds to probes destined for the gateway by
verifying the attributes that the APPL object defines for a particular user.
GROUP Objects
A GROUP is a set of one or more processes and databases that provide a defined set
of services. All groups in an OSI/MHS subsystem fall within the five classes: GI, LO,
MR, MS, and RS.
Each group, in turn, includes a single process or a set of processes Thus, in an
OSI/MHS subsystem, CLASS, GROUP, and PROCESS are successively less inclusive
categories:
•
The GI class includes all the GI groups. Each GI group contains one gateway
interface (GI) process.
•
The LO class includes all the LO groups. Each LO group contains one local
operations service (LO) process.
•
The MR class includes all the MR groups. Each MR group contains a message
relay (MR) process, a reliable transfer service (RTS) process, and a store cleaner
(SC) process.
•
The MS class includes all the MS groups. Each MS group contains one message
store (MS) process.
•
The RS class includes all the RS groups. Each RS group contains one remote
operations service (RS) process.
GROUP object attributes specify characteristics like the following:
•
Names and priorities of processes
•
CPUs where the processes run
•
PDU stores and log files the group will use
•
In the case of MR and RS groups, the OSI addresses used for accepting
associations. (The MR group accepts associations from adjacent MTAs; the RS
group accepts them from remote user agents.)
When you use SCF or a management application to operate on a GROUP object, the
command affects the processes (and potentially, the data files) associated with the
group. To create or delete a process, or to change its state or attributes, you direct a
command to the group in which that process is defined. For example, to create an RS
process, you add an RS group. A few SCF informational commands affect PROCESS
objects directly. See PROCESS Objects on page 2-63.
Using the GROUP object type, you can: