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-9

Transferring Data

Sending P7 Submission and Retrieval Arguments

After you have established an application association, you can send a P7 submission or

retrieval request to the OSI/MHS subsystem. To send data, you use the

LOS_DT_SEND_ procedure call to send the P7 argument. The P7 argument is an

encoded ROSE encapsulated P7 operation. You then call the Guardian AWAITIOX

procedure to wait for completion on the send file, and the LOS_DT_FINISH_SEND_

procedure to check for completion on the send file.

The following subsections describe the submission and retrieval operations.

Submission Operations. The P7 API supports the following submission operations:

•

MESSAGE SUBMISSION

•

PROBE SUBMISSION

•

CANCEL DEFERRED

When a client application submits a PROBE SUBMISSION or a CANCEL DEFERRED

operation, the request passes from the client application to the LO group, then from the

LO group to the MS group.

When a client application submits a MESSAGE SUBMISSION operation, the message

passes from the client application to the LO group, then to either the MS group or the

MR group, depending on the value of the SUB-RELIABLE-TRANSFER attribute

specified in the configuration setup. SUB-RELIABLE-TRANSFER can be either ON

or OFF.

When SUB-RELIABLE-TRANSFER-ON is specified, the P7 API:

•

Allows messages to be submitted once and only once.

Invoke identifier:used in message submission;

When a message is submitted, the LO group creates a record of the invoke identifier, the

APPL object performing the submission, and the PDU reference number. This

information is stored in a log file in the MR PDU.

Figure 2-3. Binding to an MS Group

203CDT .CDD

OSI/MHS Subsystem

Client

Application

API

MS Group

LO Group