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

Procedure Calls
OSI/MHS P7 Application Programmatic Interface (P7 API) Manual—424825-001
3-2
Procedure Names and Categories
disk is the name of the volume where the software is located. By default, the Install
program places these files on $SYSTEM. The actual location of these files can be
$SYSTEM or another volume chosen by your site.
For applications coded in C, you must use the #include preprocessor directive to
include the P7PIEXTH file in your program before making any calls to the procedures.
For applications coded in TAL, you must use the ?SOURCE directive to include the
P7PIEXT file at the beginning of the external procedures section of your program.
You can also use the #include preprocessor directive to include the ZMHSC file in
your C application programs and the ?SOURCE directive to include the ZMHSTAL file
in your TAL application programs. These files are the same ones used by the OSI/MHS
subsystem. These files files contain the DDL constants used by client applications when
calling the P7 API procedures.
Procedure Names and Categories
rThe names of all P7 API procedures start with the prefix LOS_ . LOS stands for local
operations server. The P7 API procedures fall into two categories:
•
P7 API environment-management procedures which enable you to initialize and
manage a P7 API session. The names of these procedures have only the LOS_
prefix.
•
P7 API data-transfer procedures which enable you to send data to and receive data
from OSI/MHS. The names of these procedures begin with the prefix LOS_DT_ .
DT stands for data transfer.
Table 3-2 summarizes the environment-management and data-transfer procedures and
the function of each one.
Note. When you refer to a DDL name in a C program, you must substitute an underscore (_)
for each hyphen in the name. You must also use uppercase and lowercase letters as they
appear in the ZMHSC file.
When you refer to a DDL name in a TAL program, you must substitute a carat (^) for each
hyphen in the name.
Table 3-2. P7 API Procedures
Environment-Management Procedures
Procedure Name Purpose
LOS_CLOSE_ Ends a P7API session between a client application and the
P7API
LOS_INITIALIZE_ Sets up an environment in which other P7API procedures can
operate. This procedure must be the first procedure called by
the client application.
LOS_OPEN_ Establishes a P7API session between a client application and
the P7API. This procedure must be called before calling any
data-transfer procedures.