Expand Management Programming Manual

EVENT MANAGEMENT
Event-Management Programming
EVENT-MANAGEMENT PROGRAMMING
The buffer size for an EXPAND event message is 128 words.
EXPAND event messages are made up of individual tokens, each
containing one piece of information about the event. There
are no extensible structured tokens or lists in EXPAND event
messages.
All EXPAND event messages are reported to EMS and none are
reported to the Tandem Maintenance and Diagnostic System (TMDS).
All messages are also displayed on the operator console con-
trolled by the compatibility distributor ($Z0).
The EXPAND subsystem does not report any events as action events
(events that require operator intervention).
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 EXPAND
subsystem, a filter would examine the token that contains the
subsystem ID of the issuing subsystem and pass through only those
messages containing the EXPAND 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 that return only critical event messages, all
event messages associated with a particular device, all event
messages with a certain event number, and so forth.
For more information about filters, refer to the Event Management
Service (EMS) Manual .
EVENT-MESSAGE DESCRIPTIONS
On the following pages, each event message that can be issued by
the EXPAND subsystem is described in detail. The descriptions
are given in ascending order by event number; that is, in
ascending order by the ZEXP-EVT- values.
8-4