SPI Programming Manual (G06.24+, H06.03+, J06.03+)

Introduction to SPI
SPI Programming Manual—427506-006
1-8
SPI Data Definitions
•
From C using the tal interface declaration
•
From COBOL using the ENTER TAL construct
•
From TACL using special built-in functions
•
From TAL
SPI Data Definitions
Tokens, values, command numbers, message headers, and error numbers are some
of the SPI-defined data items that are used to build SPI messages. These items are
defined using the DDL and are provided to programmers in definition files with names
beginning with ZSPI. A definition file specifically suited to each programming language
is supported by SPI:
You can use these predefined items by adding the definitions from the appropriate
definition file to their source code. In the case of TACL, load the SPI TACL definitions
or attach the ZSPISEGF segment file.
NonStop Kernel subsystems supply additional definitions in files with names beginning
with Zsss, where sss is a subsystem abbreviation. (See Appendix D, NonStop Kernel
Subsystem Numbers and Abbreviations.) All items defined in these files also have
names beginning with Zsss, where sss is the subsystem abbreviation. User-defined
definitions begin with a letter other than Z to avoid possible conflicts with HP
definitions.
SPI data definitions are developed using the DDL. See Appendix B, Summary of DDL
for SPI. For a complete description of DDL, see the Data Definition Language (DDL)
Reference Manual
.
SPI and EMS
The event messages created using the Event Management Service (EMS) are a form
of SPI message, and the EMS procedures with which event messages are
manipulated are based on the SPI procedures. The EMS Manual describes event
messages and EMS.
SPI Debugging
Inspect, a HP debugging tool, supports two methods of displaying the contents of SPI
messages. See the Inspect Manual and the DSM Template Services Manual .
Programming Language Definition File
CZSPIC
COBOL ZSPICOB
TACL ZSPITACL
TAL SZPITAL