Using SPI
Using Programmatic Interfaces
107365 Tandem Computers Incorporated
7–7
Table 7-2. SPI Token Data Types (Page 2 of 2)
Token Data Type Name
Value Type and Range
ZSPI^TDT^SSCTL
0 to 255
ZSPI^TDT^SSID
Subsystem owner, period, subsystem number, period, and version
number.
ZSPI^TDT^STRUCT
Must be put into, or obtained from, a STRUCT. Definition of the
STRUCT provides rules for conversion between internal and external
formats.
ZSPI^TDT^SUBVOL
Any valid subvolume name; missing fields are not defaulted. Systems
whose numbers cannot be found are given number 255 on input;
system number 255 is shown as \?? on output.
ZSPI^TDT^TIMESTAMP
-(2**63) to +(2**63)-1
ZSPI^TDT^TOKENCODE
-2147483648 to +2147483647. On input, a 32-bit STRUCT can be
used.
ZSPI^TDT^TRANSID
A TMF transaction identifier formatted as follows:
\
system-name
(
crash-count
).
cpu
.
sequence
If the internal-format
trans-id
contains a crash count of zero, the
transaction ID is formatted as follows:
\
system-name
.
cpu
.
sequence
In either case, if the system is not named, the transaction ID is
formatted as follows:
cpu
.
sequence
If the name of a system cannot be found on output,
system-name
is replaced by
system-number
.
ZSPI^TDT^UINT
0 to 65535
ZSPI^TDT^USERNAME
Any valid user name; a user number cannot be used.
TACL interprets an unknown token data type as if the data type were ZSPI^TDT^INT.
Variable-Length Data Items
In TACL, the byte length appears before the data, separated from it by a space.