SNAX/APC Management Programming Manual

3 Elements of SPI Messages for
SNAX/APC
111813 Tandem Computers Incorporated 3–1
This section describes the portions of Subsystem Programmatic Interface (SPI)
messages that have specific meaning to SNAX/APC.
SNAX/APC Definition
Files
The tokens and other definitions for SNAX/APC are provided by the following six
definition files:
ZSPIDEF.ZAPCCOB contains COBOL85 definitions.
ZSPIDEF.ZAPCDDL contains DDL definitions.
ZSPIDEF.ZAPCTACL contains TACL definitions.
ZSPIDEF.ZAPCTAL contains TAL definitions.
ZSPIDEF.ZAPCC contains C definitions.
ZSPIDEF.ZAPCPAS contains Pascal definitions.
You should also include the ZSPI, ZCOM, ZFIL, and ZCMK files contained in the
ZSPIDEF subvolume. If you want your program to monitor events or control the EMS
subsystem, you must also include ZEMS definitions.
Several of the following sections describe what the SNAX/APC tokens represent. For
convenience, this manual documents all structures in Data Definition Language
(DDL). A brief review of DDL can be found in the appendix “Overview of DDL for
SPI” in the SPI Programming Manual.
Naming Rules and
Guidelines for
Applications
By convention, Tandem uses names beginning with the letter Z for all definitions and
all component fields of structures in its definition files. To avoid conflicts with names
defined by Tandem, do not begin any names that you define in your applications with
uppercase or lowercase Z.