Using SPI
Using Programmatic Interfaces
7–6
107365 Tandem Computers Incorporated
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
Value Type and Range
ZSPI^TDT^BOOL
-32768 – +32767
ZSPI^TDT^BYTE
0 – 255
ZSPI^TDT^CHAR
Characters
ZSPI^TDT^CRTPID
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.
ZSPI^TDT^DEVICE
Any valid device name. Systems whose numbers cannot be found are
given number 255 on input; system number 255 is shown as \?? on
output.
ZSPI^TDT^ENDLIST
Not applicable.
ZSPI^TDT^ENUM
-32768 to +32767
ZSPI^TDT^ERROR
A subsystem ID, a period, and a number in the range -32768 to
+32767.
ZSPI^TDT^FNAME
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.
ZSPI^TDT^FNAME32
A 32-bit file name of the form used by Distributed Name Service.
ZSPI^TDT^INT
-32768 to +32767
ZSPI^TDT^INT2
-2147483648 to +2147483647
ZSPI^TDT^INT4
-(2**63) to +(2**63)-1
ZSPI^TDT^LIST
Not applicable
ZSPI^TDT^MAP
Must be put into, or obtained from, a STRUCT. Definition of the
STRUCT provides rules for conversion between internal and external
formats.