X25AM Management Programming Manual

Event Management
X25AM Management Programming Manual—528037-001
7-3
Event-Management Programming
Event-Management Programming
The buffer size for an X25AM event message is 512 bytes.
X25AM 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
X25AM event messages.
All X25AM 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 compatibility distributor ($Z0).
The X25AM 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 X25AM subsystem, a filter
would examine the token that contains the subsystem ID of the issuing subsystem and
pass through only those messages containing the X25AM 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, see the EMS Manual.
Event-Message Descriptions
On the following pages, each event message that can be issued by the X25AM
subsystem is described in detail. The descriptions are given in ascending order by
event number; that is, in ascending order by the ZX25-EVT- values.
Within each event-message description, there is a box that lists all the tokens that can
appear in the event message. Header tokens are listed here, because an application
can filter event messages on header tokens as well as on other tokens.
Tokens can be unconditional, conditional, or HP internal. An unconditional token is a
token that is always present in a particular event message. A conditional token is one
that is sometimes but not always present in a particular event message. HP internal
tokens should not be used by an application.
The notation used in the box for simple tokens is a shorthand version of the essential
information given in the DDL TOKEN-CODE statement.
With the exception of the token ZEMS-TKN-SUBJECT-MARK and the token listed after
it, the order of the tokens in the box is not necessarily the order in which they will