OSI/AS Programming Manual

3 APS Procedure Calls
056783 Tandem Computers Incorporated 3–1
This section contains detailed reference information for all of the APS procedures
provided with the OSI/AS subsystem. The information includes:
A description of each procedure
The syntax of each procedure
Parameter descriptions for each procedure
Considerations (added information about the procedure)
Before using this section, you should be familiar with the material in Section 2. For
many of the procedure calls, you will also need to refer to the DDL structure and value
definitions in Appendix A.
Files Provided by
Tandem
The external declarations for the current version of the APS procedures are provided
in the system files $SYSTEM.SYSTEM.EXTDECS0 (TAL declarations) and
$SYSTEM.SYSTEM.CEXTDECS (C declarations). For applications coded in TAL, you
must include a SOURCE EXTDECS0 statement (with the appropriate APS procedure
names in parentheses) at the beginning of the external procedures section of your
program. For applications coded in C, you must include CEXTDECS in your program,
preferably before making any calls to the procedures.
The distribution subvolume for the Tandem OSI/AS product supplies three files
containing data declarations. The file ZAPSTAL contains TAL declarations for data
structures used in parameters to the procedure calls; you can use the ?SOURCE
directive to include these declarations in your TAL application programs. The file
ZAPSC contains the corresponding C declarations; you can use #include to include
them in C programs. The file ZAPSDDL is the DDL source from which the ZAPSTAL
and ZAPSC declarations were produced. For a detailed description of the structures
in ZAPSDDL, refer to Appendix A.
Procedure Names he names of all APS procedures start with the characters “APS_”. The APS procedures
fall into four major categories, identified by the last few characters in the procedure
name:
REQ_ procedures enable you to make requests to the service provider. An
example is APS_ACTIVITY_ENDREQ_ , which requests the service provider and
the remote application to end the current activity. The names of these procedures
all end with “REQ_”.
RSP_ procedures enable you to respond to an incoming indication primitive. An
example is APS_ASSOC_RELEASERSP_ , which lets you respond to a release
indication from the remote application. The names of these procedures all end
with “RSP_”.
GETPARAM_ procedures make the parameters of incoming primitives, and other
information related to those primitives, available to your application. An example
is APS_DATA_GETPARAM_ , which makes transmitted user data available to
your application. The names of these procedures all end with “GETPARAM_”.