GDSX Management Programming Manual

Event Messages

GDSX Management Programming Manual—529930-001

6-3

Programming Considerations

GDS event messages do not contain extensible structured tokens or lists. The event-

message buffer size is 128 words.

All GDS event messages are reported to EMS and none are reported to the HP

Tandem Maintenance and Diagnostic System (TMDS). All messages are also

displayed on the operator console controlled by the capability distributor ($Z0).

The GDS subsystem does not report any events as action events (events that require

operator intervention).

Strategies

EMS provides you with the capability to create programs called filters, which allow

applications to select particular event messages from among all the event messages

that have been issued. Filters select event messages to be returned to an application

by examining the values of tokens in the event message.

For example, to select only event messages issued by the GDS subsystem, a filter

would examine the token that contains the subsystem ID of the issuing subsystem and

pass through only those messages containing the GDS subsystem ID.

Any of the tokens in an event message can be used for selecting the event messages

to be returned to an application. You can create filters to return messages of a certain

type only, like all critical event messages, all event messages associated with a

particular device, all event messages issued during a particular time period, or all event

messages with a certain event number.

Event Message Tokens

This subsection provides information on three kinds of tokens: header token, a

standard EMS token, and subsystem-specific tokens.

Header Tokens

Table 6-2 lists the standard EMS tokens that appear in an event-message header; they

are unconditional tokens.