OSI/MHS Management Programming Manual

Introduction to Management Programming for
OSI/MHS
OSI/MHS Management Programming Manual—424824-001
1-4
Why Use Management Programming for OSI/MHS?
Why Use Management Programming for OSI/MHS?
In some situations, it is desirable to use a programmatic interface, rather than an
interactive interface, to manage a subsystem such as OSI/MHS. This is true for the
following reasons:
•
It is efficient to transfer as many routine network-management tasks as possible to
programs running on the computer network, freeing operators and other network-
management personnel.
•
Information obtained through the programmatic interfaces can be used directly by an
application to determine how to proceed, to produce reports, and so forth.
An application that uses the programmatic interfaces to subsystems can perform tasks
that once required the use of several different interactive interfaces. In addition, the
capability to write your own management applications allows you to tailor them to the
needs and configuration of your network.
OSI/MHS Subsystem Architecture
OSI/MHS is a set of processes that implement the CCITT X.400 recommendations.
These processes are organized into groups and include:
•
Message relay process (MRP)
Encodes and decodes message headers, routes messages, and schedules messages
for delivery
•
Reliable transfer service (RTS) process
Provides the interface to OSI/AS and ensures reliable transfer of messages
•
Store cleaner (SC) process
Deletes processed protocol data units (PDUs) from the PDU store
•
Message store (MS) process
Manages the mail boxes in which messages are stored
•
Remote operations service (RS) process
Provides the interface from a remote user agent to a user mailbox in the message
store, using the OSI services
•
Local operations service (LO) process
Provides a direct interface from a local user agent to a user mailbox in the message
store, without using the OSI services
•
Gateway interface (GIP) process
Allows access to the Gateway Programmatic Interface (GPI)
OSI/MHS is built upon Open Systems Interconnection/Application Services (OSI/AS)
and its underlying subsystems. OSI/MHS requires Compaq OSI/AS, Compaq OSI/TS
(Transport Service), plus one of the following Compaq access methods:
•
X.25 Access Method (X25AM, for wide area networks)
•
Tandem LAN Access Method (TLAM, for local area networks) for D-series releases