TCP/IP TELNET Management Programming Manual

Event-Management Programming
Event Management
7–2 53474 Tandem Computers Incorporated
Event-Management
Programming
TELNET event messages are made up of individual tokens, each containing one piece
of information about the event. These event messages contain no extensible structured
tokens or lists.
All TELNET event messages are reported to the EMS collector ($0).
The TELNET subsystem does not report action events. Action events prompt the
operator for intervention, such as to mount a tape. For more information about action
events, refer to the Event Management Service (EMS) Manual.
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 that are going 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 TELNET subsystem, a filter
would examine the token that contains the subsystem ID of the issuing subsystem and
pass through only those messages containing the TELNET subsystem ID.
Any of the tokens in an event message can be used for selecting the event messages
that are going to be returned to an application. You can create filters that return only
critical event messages, that return 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
This subsection describes each event message that can be issued by the subsystem.
The descriptions are given in ascending order by event number; that is, in ascending
order by the ZTNT-EVT- values.
Each event-message description contains 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 by header tokens, such as ZSPI-TKN-SSID, as well as by other tokens.
The order in which tokens are presented in the token sections of the syntax box is
arbitrary, except that the token ZEMS-TKN-SUBJECT-MARK always immediately
precedes the subject token of an event message. For more information on the subject
token, refer to the Event Management Service (EMS) Manual.
The syntax box also contains a portion of the text version of the event message. The
text version of an event message is available through the EMSTEXT procedure. The
text contains a standard header that includes the date, time, system name, and other
information. (For further information on the standard header, refer to the Event
Management Service (EMS) Manual.) The text shown in the box follows this standard
header.
When you use the EMSTEXT procedure to get the text version of an event message,
you request either the display format version or the console-compatible format version
as described in the Event Management Service (EMS) Manual. In the case of TELNET