GDSX Management Programming Manual
Communicating With GDSX
GDSX Management Programming Manual—529930-001
2-4
Event Numbers
$GDS.*.*. Section 1 describes the kinds of objects the GDS subsystem manages. The
names of all object types are defined in Section 4, Common Definitions.
Event Numbers
In the GDS subsystem, event numbers are represented by symbolic names of the form
ZGDS-EVT-name, where name identifies the event. Each event message is assigned a
different number. GDSX event message numbers and their associated event
messages are described in Section 6, Event Messages.
Subjects for Event Messages
An event-message subject is the token that immediately follows the subject-mark
token.
In GDS subsystem event messages, the subject token is the process name. Its token
code is ZGDS-TKN-PROCNAME. To retrieve the value of the subject token, you must
first call EMSGET with the token code ZEMS-TKN-SUBJECT. This provides the token
code and index of the subject token. Then call EMSGET again with this token code
and index to get the value of the subject token.
Other Tokens
In addition to the tokens described above, the GDS subsystem uses tokens for
command parameters, results in responses, and event message elements.
Simple Tokens
Simple tokens contain values that are single fields or fixed structures; they are
identified by token codes. The token codes for the simple tokens used by the GDS
subsystem are represented by symbolic names of the form subsys-TKN-name, where
subsys is a four-character subsystem abbreviation and name identifies the token
code. For example, the token code ZGDS-TKN-ID identifies a simple token that
contains the product number and date for the GDSX version.
Token Types
A token type is a part of the token code that consists of the token data type (such as
signed integer) and the token length (such as two bytes). Token types are represented
by symbolic names of the form subsys-TYP-name, where subsys is the four-
character subsystem abbreviation and name identifies the token type. For example,
the GDS subsystem uses ZSPI-TYP-FNAME32. There are no token types specific to
the GDS subsystem. Throughout this book, the token type of each token will be
indicated where the token is described.