OSI/MHS Configuration and Management Manual

Introduction to OSI/MHS
OSI/MHS Configuration and Management Manual—424827-003
1-19
Local Operations Service (LO) Group
An RS group contains the following:
•
Remote operations service (RS) process
•
RS PDU store
An OSI/MHS subsystem can have zero, one, or more RS groups. If the subsystem
includes MS groups, it must have at least one RS group.
Remote Operations Service (RS) Process
The RS process is a single, restartable process that provides the following functions:
•
Interfaces to the OSI/AS services
•
Manages associations from remote UAs
•
Encodes and decodes messages
•
Creates and deletes PDUs in the MR or MS PDU stores as submittal and retrieval
operations are successfully completed
•
Provides Remote Operations Service Element (ROSE) functions
The RS process is a multithreaded process in that it allows you to manage multiple
associations simultaneously.
RS PDU Store
Each RS group has one PDU store. The PDU store consists of a data file and a log file.
The data file contains the encoding and decoding information for the RS operations.
The log file contains records that indicate the processing steps taken on specific PDUs.
The RS PDU store serves as a work file for the RS group. These files are defined for
each RS group.
Local Operations Service (LO) Group
The local operations service (LO) group provides an interface from a local UA to a user
mailbox in a message store. The LO group implements, for local users, functions
analogous to those of the Remote Operations Service Element (ROSE) protocol. The
P7 Application Programmatic Interface (P7 API) allows you to access an MS through
the LO group. The LO process supports local MS users by processing the MS bind and
selecting the appropriate MS group to process the requested operations.
When a user at a workstation connects to or dials up the message store, the local UA
sends a bind request into the system. The LO 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 LO group has to identify the user who sent the bind request
and determine in which MS group the mailbox for that user is located. Any LO group
can communicate with any MS group.