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

SPI Programming in TACL
SPI Programming Manual—427506-006
8-17
#SSPUTV
COUNT count
gives the token count. If count is greater than 1, source-var is assumed to
contain an array of
count elements, each of which is described by the
token-id. If you do not supply this option, TACL assumes a count of 1.
If
token-id is one of the special SPI token codes whose semantics do not
allow a token value, you must omit COUNT
count. For the special token code
ZSPI^TKN^DELETE, you must supply COUNT
count, and count is
interpreted as the index value of the token code to be deleted.
SSID ssid
is a subsystem ID, as described in Section 4, that qualifies the token code. If
ssid is not supplied or is equal to zero (0.0.0), the default applies. If SSPUT is
currently adding tokens to a list,
ssid defaults to the subsystem ID of that list;
otherwise,
ssid defaults to the subsystem ID in the SPI message header
(ZSPI^TKN^SSID).
buffer-var
is the name of the SPI message-buffer variable into which tokens are to be placed.
token-id
is a token code or a token map. This parameter either identifies the token being
supplied or denotes a special operation. The special operations are described
further in Special Operations for #SSPUT and #SSPUTV
on page 8-13.
source-var
is the name of the STRUCT from which #SSPUTV is to obtain the binary token
values. The contents of the STRUCT are not altered.
Expansion
#SSPUTV expands to a numeric status code indicating the outcome of the operation.
The status code has one of these values:
0 No error
-1 Invalid buffer format
-2 Illegal parameter value
-3 Missing parameter
-4 Illegal parameter address
-5 Buffer full
-6 Invalid checksum
-7 Internal error
-8 List token not found
-9 Illegal token code or map
-10 Invalid subsystem ID
-11 Operation not supported
-12 Insufficient stack space