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

Procedure Calls
OSI/MHS P7 Application Programmatic Interface (P7 API) Manual424825-001
3-4
LOS_CLOSE_
The remainder of this section provides the syntax and semantics of the P7 API
procedures, in alphabetic order.
LOS_CLOSE_
Use the LOS_CLOSE_ environment-management procedure to end a P7 API session
between a client application and the P7 API.
Figure 3-1. Sample P7 API Procedure Call Description
status = LOS_CLOSE_ ( sendFileNum,
resultFileNum );
301CDT .CDD
1 2 3
Legend
This indicates the type of value that the procedure returns. For the P7 API procedures, the
variable name is always
status
. Appendix A gives the
status
values that can
be returned.
This is the name of the procedure. It must appear in the program exactly as shown, including
the underscore characters. In a C program, all letters in the procedure name must be in
uppercase.
You must enclose the list of parameters in parentheses. Use commas to separate multiple
parameters.
This line indicates whether the parameter is an input or output parameter (or both).
This line indicates the parameter type, which is one of the following:
This line indicates the information passed or returned in the parameter.
16-bit integer
32-bit integer
extended pointer to 16-bit integer
extended pointer to 32-bit integer
int
long int
extptr int *
extptr long int *
1
2
3
4
5
6
status = LOS_DT_SEND_
( sendFileNum,
bufferPtr,
maxBufferLen,
dataType ) ;
status returned value
4
5
6
long init
indicates the outcome of the call ...
sendFileNum input
int
is an integer that identifies ...