HP TACL Programming Manual page 165

Table 7-2. SPI Token Data Types (Page 2 of 2)
Token Data Type Name
ZSPI^TDT^SSCTL
ZSPI^TDT^SSID
ZSPI^TDT^STRUCT
ZSPI^TDT^SUBVOL
ZSPI^TDT^TIMESTAMP
ZSPI^TDT^TOKENCODE
ZSPI^TDT^TRANSID
ZSPI^TDT^UINT
ZSPI^TDT^USERNAME
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.
107365 Tandem Computers Incorporated
Value Type and Range
0 to 255
Subsystem owner, period, subsystem number, period, and version
number.
Must be put into, or obtained from, a STRUCT. Definition of the
STRUCT provides rules for conversion between internal and external
formats.
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.
-(2**63) to +(2**63)-1
-2147483648 to +2147483647. On input, a 32-bit STRUCT can be
used.
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 .
0 to 65535
Any valid user name; a user number cannot be used.
Using Programmatic Interfaces
Using SPI
7–7