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

OSI/MHS P7 Application Programmatic Interface (P7 API) Manual—424825-001
A-1
A
DDL Definitions
This appendix describes the data structures and external constants that you can use in
parameters to the P7 API procedures. These structures and constants are expressed in
the Data Definition Language (DDL). You receive the DDL in two forms:
•
The equivalent of C code (in the file ZMHSC) is provided for you to include in your
C program by using the #include directive.
•
The equivalent of TAL code (in the file ZMHSTAL) is provided for you to include
in your TAL program by using the ?SOURCE directive.
In the headings in this section, the abbreviation xxx is used to indicate the remainder of a
DDL name that follows a prefix. DDL definitions used to return status and error
information from the P7 API procedures are described in Appendix B, “Return Codes.”
Data Structures
There is only one DDL data structure that you can use in a P7 API client application.
This data structure specifies the size of the buffer that is used internally by the P7 API to
send data between the P7 API library and the LO process.
External Constants
The external constants that you can use in a P7 API client application are:
ZMHS-VAL-EM-xxx
ZMHS-VAL-EM-NO-WAIT
specifies that all data transfer operations to the send and result files are nowait
operations.
Note. When the DDL compiler translates these definitions into C, the compiler changes
hyphens ( - ) in the names to underscores ( _ ). When the DDL compiler translates these
definitions into TAL, the compiler changes hyphens ( - ) in the names to carats ( ^ ).
You should use underscores in DDL names included in your C programs and carats in DDL
names included in your TAL programs. Additionally, because the C language distinguishes
uppercase and lowercase letters, you must use the DDL names exactly as they are declared in
the ZMHSC file or create your own declarations file.
zmhs-ddl-uapi-request-def VALUE
NO-WAIT VALUE 141