OSI/MHS Configuration and Management Manual

Introduction to OSI/MHS

OSI/MHS Configuration and Management Manual—424827-003

1-18

Remote Operations Service (RS) Group

presentation services of OSI/AS. Different RS groups “listen” for incoming association

requests on the same or different OSI addresses.

When a user at a workstation connects to or dials up the message store, the RUA

sends a bind request into the system. The RS group has to direct that incoming bind

request to the correct MS group for that user. (Individual users are assigned to a

particular MS group.) The RS group has to look at the identity of the user who sent the

bind request and determine which MS group contains the mailbox for that user. Any RS

group can talk to any MS group.

When a user wants to retrieve a message, the MS group finds the message in the

message store and tells the RS group where to find it in the PDU store. The body of

the message does not go through the MS group; the RS group accesses it directly

from the MS PDU store and sends it to the user.

When a user submits a message, the message request goes to the MS group. The MS

group allocates a PDU ID in the MS PDU store. Then the RS group writes the

message directly into the MS PDU store. The MS group then forwards the message to

an MR group.

Figure 1-10 shows an RS group.

Note. A PDU ID is generated by OSI/MHS for internal use by OSI/MHS processes only. This

PDU ID is not the same as the MPDU ID defined by X.400.

Figure 1-10. Remote Operations Service (RS) Group

011VS T .VS D

OSI/MHS Subsystem

RS Grou p

RS PDU

Store

OSI /AS

MS Groups

MR Groups