GDSX Management Programming Manual

Communicating With GDSX
GDSX Management Programming Manual—529930-001
2-5
Other Tokens
Predefined Value Names
The predefined values used by the GDS subsystem are represented by symbolic
names of the form subsys-VAL-name, where subsys is the four-character
subsystem abbreviation and name identifies the predefined value. For example, ZGDS-
VAL-VERSION is a predefined value name containing the value “D10.”
Extensible Structured Tokens
All GDSX commands use extensible structured tokens. Event messages issued by the
GDS subsystem do not use extensible structured tokens.
The token maps used by the GDS subsystem are represented by symbolic names of
the form subsys-MAP-name, where subsys is a four-character subsystem
abbreviation and name identifies the token map.
Throughout this manual, when a structured token is described, its DDL definition,
including the definitions and types of all fields, is also given.
The predefined field values used by the GDS subsystem are represented by symbolic
names of the form subsys-VAL-name, where subsys is a four-character subsystem
abbreviation and name identifies the predefined value.
The following example is an extensible structured token that defines a subdevice to the
GDS subsystem.
ZGDS-MAP-ADD-SU
This token map contains the following information:
•
Device name (if the default is not used)
•
Size of the subdevice
•
Associative flag
•
Autostop flag
•
Nowait I/O maximum number
•
Subdevice type
•
User data
Field Types
All field types used by the GDS subsystem are SPI standard field types and are
represented by symbolic names of the form ZSPI-DDL-name, where name identifies
the field type.
Throughout this manual, when a field is described, its field type is given.