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

Procedure Calls
OSI/MHS P7 Application Programmatic Interface (P7 API) Manual—424825-001
3-11
LOS_DT_SEND_
send plus 24 bytes. The first 24 bytes are reserved for control information and can
be allocated using the DDL constant ZMHS-VAL-DT-DATA-OFFSET.
The data in the buffer can be:
•
An MSBIND argument, which is structured like the user data in an Application
Control Service Element A-Associate Response Application Protocol Data Unit
(ACSE AARE-APDU) as if ACSE were being used.
•
A submission or retrieval argument which is a Remote Operations Invoke
Application Protocol Data Unit (ROIV-APDU), which would be contained in
the P-DATA if Presentation Layer Services were being used. It contains one of
the following arguments:
•
SUMMARIZE argument
•
LIST argument
•
FETCH argument
•
DELETE argument
•
MESSAGE SUBMISSION argument
•
PROBE SUBMISSION argument
•
CANCEL DEFERRED argument
•
REGISTER-MS argument
•
P-DATA information made up of the Remote Operations Result (RORS) APDU
for the SUBMISSION CONTROL result or the Remote Operations Error
(ROER) APDU for the SUBMISSION CONTROL error.
•
An Remote Operations Reject (RORJ) APDU if the client application is unable
to interpret the Remote Operations Invoke (ROIV) APDU.
For an MSUNBIND operation, bufferPtr is empty on input.
bufferLen input
long int
specifies the length of the data to be sent to OSI/MHS in bytes. The value specified
in ZMHS-VAL-LOUAPI-MAX-DATA-SIZE is the maximum length that you can
specify.
If the data does not fit in one buffer, specify the ZMHS-VAL-DT-MORE-DATA
value for the moreData parameter. In this case, specify a minimum length of 1K
bytes for bufferLen.
maxBufferLen input
long int
specifies the maximum length of the buffer in bytes. You must specify
ZMHS-VAL-LOUAPI-MAX-DATA-SIZE for this parameter.