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

SPI Programming Manual—427506-006
9-1
9 SPI Programming in TAL
This section provides language-specific information for the programmer who is using
the TAL to write an SPI requester or server:
Definition Names in TAL
Symbolic names in this section are in the TAL form, using circumflex (^) symbols rather
than hyphens. For example, the DDL token code ZSPI-TKN-RETCODE is expressed
as ZSPI^TKN^RETCODE in TAL.
TAL Definition Files
Each TAL module of your application that uses the Subsystem Programmatic Interface
(SPI) must begin with ?SOURCE directives to include the TAL versions of the SPI
standard definitions and the definitions for all subsystems with which your program
communicates. The TAL version of the SPI standard definitions is in the file named
ZSPIDEF.ZSPITAL on the disk volume chosen by your site.
For NonStop Kernel subsystems, the TAL versions of the subsystem definitions have
file names of the form ZSPIDEF.
subsysTAL, where subsys is the 4-character
subsystem abbreviation given in Appendix D, NonStop Kernel Subsystem Numbers
and Abbreviations. You can include these ?SOURCE directives in any order, but they
must precede any of your own declarations that refer to them.
Declarations Needed in TAL Programs
In addition to the declarations already provided in the definition files, you must add
these declarations to your TAL programs:
SPI Buffer
The ZSPIDEF.subsysTAL definition file for each NonStop Kernel subsystem includes
a buffer declaration named
subsys^DDL^MSG^BUFFER^DEF, which has the
Topic Page
Definition Names in TAL
9-1
TAL Definition Files 9-1
Declarations Needed in TAL Programs 9-1
Interprocess Communication 9-3
SPI Procedure Syntax in TAL 9-3
Examples 9-5