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

Glossary
SPI Programming Manual—427506-006
Glossary-14
token data type
(16 bits) and a token number (16 bits). In TAL, TACL, and COBOL, names are used to
represent token codes (ZSPI-TKN-SSID, for example). In DDL, a special definition
(using the TOKEN-CODE statement) that the DDL compiler translates into an SPI
token code. Token codes have symbolic names of the form
subsys-TKN-name. See
also token map
and qualified token code.
token data type. The part of the token code that defines the kind of value (such as an
integer or a file name) allowed for a token. Token data types have symbolic names of
the form
subsys-TDT-name.
token length. The part of a token code that indicates the length in bytes of the
corresponding token value. A token length of 255 indicates that the token value has
variable length or a length greater than 254, in which case the first word of the token
value contains the (noninclusive) byte length of the rest of the token value.
token map. An SPI structure that describes the fields of an extensible structured token.
Also, a variable name used to refer to an extensible structured token. The token map
includes a token code and a description of the token value: its fields, the null values of
those fields, and the versions of the fields. A token map defines a structure that might
change in some later code version (by the addition of new fields at the end), and the
information in the map allows SPI to provide compatibility between different structure
versions. In DDL, a special definition (using the TOKEN-MAP statement) that the DDL
compiler translates into an SPI token map. Token maps have symbolic names of the
form
subsys-MAP-name.
token number. The number used by a subsystem to identify each token that it defines. The
token type and the token number together form the token code. Token numbers have
symbolic names of the form
subsys-TNM-name.
token type. In SPI, a combination of the token data type and token length; part of the token
code. In DDL, a special definition (using the TOKEN-TYPE statement) that the DDL
compiler will translate into an SPI token type. Token types have symbolic names of the
form
subsys-TYP-name.
token value. The value assigned to a token.
token-oriented. Programmatic interfaces that convey information in tokens, code-value
pairs accessed by code rather than by address or ordinal position. SPI is a token-
oriented programmatic interface.
upward compatibility. The ability of a requester to operate gracefully with a server of a
higher version. In this case, the requester is upward-compatible with the server, and
the server is downward-compatible with the requester. Compare with downward
compatibility.
version compatibility. The ability of a requester and server of different revision levels to
operate gracefully together.