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

SPI Concepts and Protocol
SPI Programming Manual—427506-006
2-13
Definition Files Supplied by HP
Definition Files Supplied by HP
The data definitions provided by HP for the NonStop server are distributed in standard
definition files, normally located in $
release-vol.ZSPIDEF.* (although they can be
placed elsewhere). The file names begin with the 4-character subsystem abbreviation
subsys; for example, ZSPIDDL, ZEMSDDL, and ZCOMDDL. Language-specific files
for TAL, COBOL, TACL, and C are generated from each DDL file. They have names
like ZSPI
TAL, ZSPICOB, ZSPITACL, and ZSPIC. An Expand management application
written in TAL might require these files:
SPI Message Buffer
SPI messages are composed in a specially allocated block of memory called an SPI
buffer. An SPI buffer consists of a header, which contains message information
common to all command and response messages, and a variable-length body
containing message tokens. The logical structure of an SPI buffer is shown in
Figure 2-3
on page 2-14.
subsys ZCOM (an extended SPI definition)
type TKN (a token code)
description OBJNAME (value conveyed by token: an object name)
ZSPIDEF.ZSPITAL Definitions common to all subsystems
ZSPIDEF.ZCOMTAL Definitions for common SPI extensions
ZSPIDEF.ZEMSTAL Event (EMS) definitions common to all subsystems
ZSPIDEF.ZEXPTAL Expand definitions