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

Procedure Calls
OSI/MHS P7 Application Programmatic Interface (P7 API) Manual—424825-001
3-12
LOS_DT_SEND_
moreData input
int
specifies whether there is more data to be sent. The values are
ZMHS-VAL-DT-MORE-DATA and ZMHS-VAL-DT-NO-MORE-DATA.
dataType input
int
specifies the data type of the data to be sent. dataType can be:
ZMHS-VAL-DT-MS-BIND-ARG
ZMHS-VAL-DT-MS-UNBIND-ARG
ZMHS-VAL-DT-P-DATA
For MSBIND and P-DATA, bufferPtr contains the associated data. For
MSUNBIND, bufferPtr is empty.
Considerations
•
To send a message that does not fit in one buffer, use multiple calls to
LOS_DT_SEND_ and set the moreData parameter in all but the last call to
ZMHS-VAL-DT-MORE-DATA. Set the parameter in the last call to
ZMHS-VAL-DT-NO-MORE-DATA.
•
For the REGISTER-MS operation LOS_DT_SEND_ can contain the change-
credentials, list-attribute-defaults, and fetch-attribute-defaults arguments only.
These are the only arguments accepted in this implementation.
•
Because a client application must complete a send before attempting to send another
PDU, you should consider using a queuing function. In this case, the client
application should:
•
Remove entries from the queue only after receiving the response PDU that
references the original invoke ID.
•
Consider using the Transaction Monitoring Facility (TMF) to bracket the
transactions. The application could start a TMF transaction before a call to
LOS_DT_FINISH_RESULT_ and end the transaction after deleting the invoke
PDU from the queue and accepting or not accepting the response. If you choose
to use TMF, you should note that the transaction IDs are not transferred to the
LO process.
•
For each active client application, the P7 API can keep track of up to 10 message
submissions for which a response has not been received. If there are more than 10
outstanding message submissions when a process failure occurs, a message might be
duplicated. To avoid message duplication, use the SUB-RELIABLE-TRANSFER
ON attribute with ON specified.
If the client process stops after issuing a P7 SUBMIT operation but before receiving
the response, the client application should reinitialize the P7 API environment,
reopen a session, rebind to an MS group, and reissue the SUBMIT operation using
the original invoke identifier (ID).