Table 7-2 Spi Token Data Types - HP TACL Programming Manual

Using Programmatic Interfaces
Using SPI
7–6
TANDEM.EMS.0 and TANDEM.43.1245 are examples of valid subsystem IDs for
Tandem subsystems.
The following considerations apply to the use of subsystem IDs in TACL:
The null subsystem ID (all binary zeroes) is expressed as 0.0.0 in TACL.
TACL performs automatic conversion between text and the internal format used
by SPI for subsystem IDs.
Your TACL function must specify the subsystem ID for each subsystem with
which your application communicates.
Token Data Types
TACL supports the token data types listed in Table 7-2.
Table 7-2. SPI Token Data Types (Page 1 of 2)
Token Data Type Name
ZSPI^TDT^BOOL
ZSPI^TDT^BYTE
ZSPI^TDT^CHAR
ZSPI^TDT^CRTPID
ZSPI^TDT^DEVICE
ZSPI^TDT^ENDLIST
ZSPI^TDT^ENUM
ZSPI^TDT^ERROR
ZSPI^TDT^FNAME
ZSPI^TDT^FNAME32
ZSPI^TDT^INT
ZSPI^TDT^INT2
ZSPI^TDT^INT4
ZSPI^TDT^LIST
ZSPI^TDT^MAP
107365 Tandem Computers Incorporated
Value Type and Range
-32768 – +32767
0 – 255
Characters
Any valid process name or cpu , pin . Systems whose numbers
cannot be found are given number 255 on input; system number 255
is shown as \?? on output. The creation time of any unnamed process
or the cpu , pin of a named process can be accessed only by
redefining the fields appropriately.
Any valid device name. Systems whose numbers cannot be found are
given number 255 on input; system number 255 is shown as \?? on
output.
Not applicable.
-32768 to +32767
A subsystem ID, a period, and a number in the range -32768 to
+32767.
Any valid file 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.
A 32-bit file name of the form used by Distributed Name Service.
-32768 to +32767
-2147483648 to +2147483647
-(2**63) to +(2**63)-1
Not applicable
Must be put into, or obtained from, a STRUCT. Definition of the
STRUCT provides rules for conversion between internal and external
formats.