OSI/MHS P7 Application Programmatic Interface (P7 API) Manual

Planning and Writing Your Application
OSI/MHS P7 Application Programmatic Interface (P7 API) Manual—424825-001
2-5
Managing the P7 API Environment
received, you then call the LOS_DT_FINISH_SEND_ procedure if completion occurred
on a send file, or LOS_DT_FINISH_RESULT_ if completion occurred on a result file.
For a description of the AWAITIOX procedure, see the Guardian Procedure Calls
Reference Manual.
Figure 2-1 shows the task sequence in the form of a flow diagram.
The following subsections describe the operations performed by the P7 API
environment-management and data-transfer procedures. P7 operations are sent and
received by the data-transfer procedures. Data-transfer procedures are described in
X.413 MHS: Message store: abstract service definition in Recommendations X.400-
X.420 (1988).
Managing the P7 API Environment
Your client application must manage a run-time environment for P7 API procedures.
The environment has two key elements: a memory space dedicated to the P7 API
procedures and a session that links the client application to the OSI/MHS subsystem.
The tasks described in this subsection are:
•
Initializing the P7 API environment
•
Opening a P7 API session
•
Closing a P7 API session
Figure 2-1. P7API Program Flow
201CDT .CDD
P7 API Procedure
Open a Session
Program Flow
Initialize Workspace
LOS_CLOSE_
Close a Session
LOS_DT_SEND_
LOS_DT_FINISH_SEND_
LOS_DT_FINISH_RESULT_
Perform P7 Operations
LOS_OPEN_
LOS_INITIALIZE_
AWAITIOX
AWAITIOX
Guardian Procedure