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

Procedure Calls
OSI/MHS P7 Application Programmatic Interface (P7 API) Manual—424825-001
3-13
LOS_INITIALIZE_
A client application should not reuse an invoke ID until it either receives the
response from the OSI/MHS subsystem or it issues an MSUNBIND operation.
MSUNBIND should be issued only after responses have been received for all
outstanding transactions.
•
A description of the content of the buffer can be found in 1988 CCITT
recommendations as follows:
•
X.413 MHS: Message store: abstract service definition contains the protocol
definitions for MSBIND, SUMMARIZE, LIST, FETCH, DELETE, and
REGISTER-MS arguments.
•
X.411 MHS: Message transfer system: abstract service definition and
procedures contains the protocol definitions for the MESSAGE SUBMISSION
argument, PROBE SUBMISSION argument, CANCEL DEFERRED argument,
and SUBMISSION CONTROL result and error.
•
X.229 Remote operations: protocol specification contains the protocol
definition for ROIV-, RORS-, ROER-, and RORJ-APDUs.
•
X.227 OSI: Association Control: protocol specification contains the protocol
definition for ACSE AARE-APDU user information.
Example
This example shows a call to LOS_DT_SEND_ .
/* GLOBALs */
#define MAX_CONNECTIONS ZMHS_VAL_LOUAPI_MAX_NUM_SESS
static int sendFileNum[MAX_CONNECTIONS]
/* Local */
int connection; /* Logical connection to */
/* perform operation on */
char *buffer[]; /* Data to be sent*/
long int dataLen; /* Length of data to send */
long int maxDataLen; /* Length of data to send */
status = LOS_DT_SEND_(sendFileNum[connection],
(int *) buffer,
dataLen,
maxDataLen,
ZMHS_VAL_DT_NO_MORE_DATA,
ZMHS_VAL_DT_MS_BIND_ARG);
LOS_INITIALIZE_
Use the LOS_INITIALIZE_ environment-management procedure to set up an
environment in which other P7 API procedures can operate. You should call this
procedure before calling any other P7 API procedures in your client application.
status = LOS_INITIALIZE_ (void)