OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide

Introduction
OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide—424822-001
1-7
NORMAL Outbound Processing
NORMAL Outbound Processing
Outbound processing is done on information outbound from the client to X.400. The
information originates as a proprietary system message (Figure 1-7).
Using GPI procedure calls, the client builds the information into a root object in GPI
library memory space. The root object is the functional equivalent of a message, probe,
report, or P1-encoded object. During this process, the client can also edit, inspect or
copy all or any part of the root object.
After the root object is formed, the client calls the GPI service to transfer it to the GPI
service output queue. The queue is logically associated with the OSI/MHS MR group
PDU store. As it passes through the GIP on its way to the queue, the root object is
encoded into a form suitable for transfer by the OSI/MHS MTA.
Figure 1-7
illustrates the internal steps in NORMAL outbound processing:
1. Proprietary information is built into a root object in the GPI library memory
segment.
2. When the client initiates outbound transfer, the GPI library sends the root object to
the GIP.
3. The GIP encodes the object into a form suitable for X.400 transfer and places it in
the MR group PDU store.
4. The GIP notifies the MRP of an outbound root object in the MR group PDU store.
5. The MRP reads the outbound root object in the MR group PDU store.
Figure 1-5. Inbound and Outbound Directions
Figure 1-6. Outbound Processing
105CDT .CDD
Client
Outbound
Inbound
OSI/MHS
MTA
106CDT .CDD
X.400 Gateway
GIP
GPI Library Memory
(Object here)
(Proprietary
Message
Here)
(Outbound
Object Here)
Output
Queue
Client
GPI
Library
GPI Service
Proprietary
Message
System