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-3
Planning for Security
Planning for Security
The initiator credentials (or user’s password for the MS APPL object) passed as part of
an MSBIND operation must match those expected by the local OSI/MHS subsystem. If
the credentials are correct, the MSBIND operation is completed and the client
application can issue P7 operations. If the credentials are incorrect or the specified
originator/recipient (O/R) address is unknown to the OSI/MHS subsystem, the
OSI/MHS subsystem returns a bind error to the client application.
Writing a P7 API Client Application
Before writing a P7 API application, you should understand how the P7 API procedures
work and how to create an executable program. This subsection discusses:
•
Developing a program structure
•
Managing the environment
•
Initializing the P7 API environment
•
Opening a session
•
Closing a session
•
Transferring data
•
Binding to an MS group
•
Sending data
•
Retrieving data
•
Unbinding from an MS group
•
Creating an executable program
Developing a Program Structure
The names of the P7 API procedure calls start with the prefix LOS_ . LOS stands for
local operations server. These procedure calls are divided into two categories:
environment management and data transfer. The environment-management procedures
initialize the environment and open and close sessions. The data-transfer procedures
perform the actual P7 operations. The final structure of your client application depends
on the P7 services you require.
Table 2-1 lists the sequence of procedure calls used in a basic P7 API client application.
As shown, each procedure or group of procedures is associated with a task. The tasks
are listed in the order that most client applications would use them.
Note. Table 2-1 does not show the looping that typically occurs during the transfer of data; for
example, it does not show repeated calls to LOS_DT_SEND_ to send data in the 30,000 byte
increments allowed by the P7 API. Section 3 describes the LOS_DT_SEND_ procedure call in
detail.