OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide

Introduction
OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide—424822-001
1-9
P1-EXIT Message Flow
1. The RTS receives a root object (representing a message, probe, report, or
P1-encoded object). The RTS places the root object on the PDU store and informs
the MRP.
2. The MRP reads the root object to determine the destination.
3. If the root object is addressed to this GPI gateway, the MRP notifies the queue
manager.
4. If a wait is pending, the queue manager notifies the GIP that an inbound root object
is available. The queue manager provides the GIP with the object’s PDU ID.
5. When the client initiates inbound transfer, the GIP decodes the root object into a
form suitable for manipulation by GPI object management procedures.
6. The GIP transfers the root object to the GPI library.
7. The client program extracts information from the root object and passes the
information into the proprietary system.
P1-EXIT Message Flow
The GPI presents an optional method of inbound processing that enables the client
program to examine messages from an adjacent MTA before the MRP performs any
routing functions on the message. This option is called the P1 User EXIT (or P1-EXIT).
Figure 1-9. NORMAL Inbound Information Flow
109CDT .CDD
GPI X.400 Gateway
Compaq System
Proprietary
System
Message
GIP
Queue Manager
Wait Manager
Entry Manager
Queue File
X.400
Message
OSI/MHS Subsystem
MHS
Manager
PDU
Store
MR Group
1
7
6
5
4
3
2
MRP
Client
GPI
Library
RTS