Data Definition Language (DDL) Reference Manual

SPI Tokens
Data Definition Language (DDL) Reference Manual—529431-004
7-15
TOKEN-MAP
Lnn
is a product version string.
L
is a letter. The DDL compiler treats L as uppercase whether you
specify it as uppercase or lowercase.
nn
is a two-digit number.
constant-name
is the name of a constant in the open dictionary. The constant name must be a
valid number or Lnn value.
FOR { field-name [ { THROUGH } field-name ] } }
{ [ { THRU } ] } }
{ } }
{ group-name [ { THROUGH } group-name ] } }
{ [ { THRU } ] }.} ...
specifies one or more fields or groups within the definition identified by def-name.
field-name
is the name of a field within the definition.
group-name
is the name of a group within the definition.
A token map is a special type of token code used to identify an extensible structured
token to which new fields can be added in subsequent product versions. You identify a
token map by its token-name.
You do not specify the token type of a token map. The token type of every token map,
ZSPI-TYP-MAP, is defined by SPI; it consists of the token data type ZSPI-TDT-MAP
and a token length of 255.
You define the structure of the extensible structured token by referring to an existing
definition, def-name, in the TOKEN-MAP statement.
You must specify a VERSION or NOVERSION clause in the TOKEN-MAP statement
for every field or group of fields in the referenced definition.
•
The product version number in a VERSION clause specifies the subsystem
product version in which the field or group of fields was introduced.
•
A NOVERSION clause is used for fields whose presence is indicated by the value
of another field in the structure−an is-present field.