Data Definition Language (DDL) Reference Manual

SPI Tokens
Data Definition Language (DDL) Reference Manual—529431-004
7-14
TOKEN-MAP
def-name
specifies the definition (in the open dictionary) that defines the fields in the
extensible structured token.
SSID subsystem-id
identifies the subsystem to which the token belongs. You can specify subsystem-
id either as an ASCII character string (enclosed in quotation marks) or as the
name of a constant in the open dictionary. The value of subsystem-id must
conform to the valid external format for a subsystem ID, which consists of 1 to 8
alphanumeric characters and hyphens specifying the subsystem owner, a period, a
subsystem number or name, another period, and a product version number; for
example:
"TANDEM.43.1245"
"TANDEM.XYZ.0"
If subsystem-id is invalid, the DDL compiler rejects the token.
If you omit the SSID clause, DSM Template Services does not keep track of the
information in the TOKEN-CODE statement’s HEADING and DISPLAY clauses.
HEADING label
specifies a label that identifies the token in DSM Template Services. DSM
Template Services uses only the first 40 characters of the heading. You can
specify label either as an ASCII character string (enclosed in quotation marks)
or as the name of a constant in the open dictionary. The value of label must be
an ASCII character string.
Default label: token-name
{ VERSION { number } }
{ { "Lnn " } }
{ { constant-name } }
{ }
{ NONVERSION }
specifies whether or not a field or group of fields in the definition is associated with
a product version number. Every elementary field must be defined with either a
VERSION or a NOVERSION clause. If VERSION or NOVERSION is specified for
a group, the clause applies to each field within that group. You can specify only
one product version number for a field.
number
is an integer in the range 1 through 65,535.