OSI/MHS Configuration and Management Manual

Management Environment for OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
2-2
The OSI/MHS Databases
control commands. The MHS manager is the first process started in the subsystem
and is represented by the first object created: the MON object.
You use SCF commands or a management application to communicate with the MHS
manager. You can add, start, stop, delete, control, and monitor OSI/MHS components
through the MHS manager. The MHS manager executes your commands to configure
subsystem objects and the components they represent. The configuration data is
stored in a configuration database. You use the MHS manager to control most objects
and the subsystem processes, including the manager process itself.
The OSI/MHS Databases
In an OSI/MHS subsystem, the MHS manager process manages a variety of
databases. All are key-sequenced Enscribe files. All of the databases are protected
from inconsistency and catastrophic failure by the Transaction Management Facility
(TMF). For more information about TMF, see the following manuals:
TMF Introduction
TMF Planning and Configuration Guide
TMF Operations and Recovery Guide
TMF Reference Manual
As shown in Figure 2-1, the OSI/MHS database includes the registration database and
the configuration database. In addition, each gateway interface (GI) group, local
operation service (LO) group, message relay (MR) group, message store (MS) group,
and remote operations service (RS) group has a database for its protocol data unit
(PDU) stores, and there are MS SQL databases for each MS group. Not shown in the
figure are the distribution list and closed user group databases, which specify the
distribution lists and closed user groups defined to OSI/MHS. You determine the
location and naming conventions for all these databases when you run the installation
procedures.
Note that although a GI PDU store is defined, it is not used by current versions of
OSI/MHS.