OSI/MHS Configuration and Management Manual

Introduction to OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
1-16
Message Store (MS) Group
Message Store (MS) Group
A message store is used for long-term storage of messages. With a message store,
you do not have to be connected to the subsystem when a message arrives; you can
log on to the system through a UA whenever you want to read or send messages.
When OSI/MHS receives a message destined for an MS user (defined to OSI/MHS as
an APPL object), OSI/MHS stores the message in the mailbox for that user. An MS
group never attempts to establish a connection to the UA; it is the responsibility of the
UA to initiate a connection, log on to the MS, and issue the appropriate requests.
An MS group supports the P2, P22, and P7 protocols.
An MS group provides a single mailbox for each user it supports. OSI/MHS supports
up to 1,000 users per MS group. Figure 1-9 shows the MS group.
The MS group contains the following:
•
Message store (MS) process
•
MS SQL database
•
MS PDU store
An OSI/MHS subsystem can have zero, one, or more MS groups.
Message Store (MS) Process
The MS process is a single, restartable process that provides the following functions:
•
Mailbox management
•
Access management
•
Submittal
•
Delivery
•
Retrieval
•
Recovery
The MS process is a multithreaded process in that it allows simultaneous processing of
messages.
MS SQL Database
Each MS group has one MS SQL database. This database (along with the PDU store)
contains a single mailbox for each user, up to 1,000 mailboxes for each MS process.
During OSI/MHS installation, the MS program for all of the MS groups gets compiled
and registered into a single MS SQL catalog. At run time for the MS groups, it is
dynamically compiled into the SQL catalog for each MS group. The MS SQL catalog is
in the same volume and subvolume as the MS SQL database.