TCP/IP Management Programming Manual

Event Management
HP NonStop TCP/IP Management Programming Manual—529636-001
7-3
Event-Management Programming
ZTCI-TKN-SEV. If the value is ZTCI-VAL-SEV-FATAL, the TCP/IP process is no longer
operational. If the value is ZTCI-VAL-SEV-WARN, it is only a warning message. If the
value is ZTCI-VAL-SEV-INFO, it is an informational message only. The ZTCI-VAL-SEV-
INFO value is present if the ZEMS-TKN-EMPHASIS token has a value of
ZSPI-VAL-FALSE.
Event-Management Programming
TCP/IP 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
these event messages.
All TCP/IP event messages are reported to the EMS collector ($0).
The TCP/IP subsystem does not report action events. Action events prompt the
operator for intervention, such as the need to mount a tape. For more information
about action events, see the 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
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 TCP/IP subsystem, a filter
would examine the token that contains the subsystem ID of the issuing subsystem and
pass through only those messages containing the TCP/IP 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 with a certain event number, and so on.
For more information about filters, see the EMS Manual.
Event-Message Descriptions
This section 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 ZTCI-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 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, see the 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, and it
contains a standard header that includes the date, time, system name, and other