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

SPI Programming in TACL
SPI Programming Manual—427506-006
8-3
SPI Buffer
•
For parameters that require external-format numbers, a numeric variable (a TEXT
variable whose contents represent a number) is acceptable.
SPI Buffer
An SPI buffer in TACL is a writable variable level of type STRUCT. The definition of the
STRUCT is irrelevant to TACL, except that TACL passes its length to the SSINIT
procedure.
The ZSPIDEF.
subsysTACL definition file for each NonStop Kernel subsystem
includes a buffer declaration whose name is
subsys^DDL^MSG^BUFFER. Use this
declaration to allocate a buffer variable of the recommended size
(
subsys^VAL^BUFLEN). Some subsystems can provide additional buffer declarations
allocating different recommended buffer-size values for different commands. For
details, see the individual subsystem management programming manual.
To define a buffer larger than the recommended size in order to handle a large number
of response records per response message, you can write your own buffer declaration.
For example, you could declare an SPI buffer:
#DEF buf STRUCT BEGIN BYTE b(0:3999); END;
Subsystem ID
The external representation of a subsystem ID is an 8-character subsystem owner, a
period separator, a subsystem number, a period separator, and a version number. The
subsystem owner can contain hyphens but the first character must be alphabetic. All
three fields—the subsystem owner, the subsystem number, and the version number—
are required.
The subsystem owner must be entered exactly as specified by the subsystem (except
that you can omit trailing blanks); TACL does not case-shift it. For NonStop Kernel
subsystems, the subsystem owner is “TANDEMbb
”.
For NonStop Kernel subsystems, you can supply the appropriate mnemonic from
Appendix D, NonStop Kernel Subsystem Numbers and Abbreviations
, in place of the
subsystem number. These mnemonics are case-sensitive; all alphabetic characters
are in uppercase, and you must enter them in uppercase.
For NonStop Kernel subsystems provided by HP, and for your own subsystems if you
use the same version-number format HP uses, you can use the external form for the
version—a letter followed by two decimal digits. If you enter the letter in lowercase,
TACL upshifts it.
Examples of valid subsystem IDs:
TANDEM.EMS.G06
TANDEM.PATHWAY.G06
MYORG.1.2
MYORG.1.A00