TS/MP 2.5 Management Programming Manual

c. Call SSMOVE or SSMOVETKN to move the context token from the response buffer into
the GETEVENT command buffer. The context token is needed when your application
resends the command to get the next event.
d. Call SSGET or SSGETTKN to retrieve the token containing the event message
(ZEMS-TKN-EVENT) from the response buffer.
e. Call EMSGET or EMSGETTKN to retrieve the subsystem ID (ZSPI-TKN-SSID) and the event
number (ZEMS-TKN-EVENTNUMBER) from the event message. Together, these two tokens
identify the event message and determine what information tokens contain.
f. Call EMSGET or EMSGETTKN twice to retrieve the subject of the event message. In the
first call, retrieve the subject-mark token (ZEMS-TKN-SUBJECT- MARK) to get the token
code and index of the token identifying the subject. Then make another call to retrieve
the subject token itself.
g. Call EMSGET or EMSGETTKN to retrieve the values of other tokens from the event message.
h. If you encounter the error-list token (ZSPI-TKN-ERRLIST), make another call to EMSGET or
EMSGETTKN to retrieve the tokens inside the error list.
i. Take action appropriate to the information in the event message.
The EMS Manual provides information on EMS collectors and on how to retrieve tokens from an
event message.
Event-Management Considerations
The overall goal of event reporting by the Pathway subsystem is to allow the system operator or a
management program to monitor and control the operation of the subsystem. The Pathway subsystem
reports events to EMS but not to the TMDS.
The maximum buffer size needed for any Pathway event message is 4024 bytes.
Some Pathway subsystem event messages contain extensible structured tokens providing information
for use by your application. In addition, some event messages contain error lists. Some of these
error lists provide information for use by your application; others contain information you report
to your HP representative. The descriptions of individual event messages explain what to do with
each error list.
Filters
EMS provides you with the ability to create filters, which allow applications to select particular
event messages from among those reported. Filters select messages to be returned to an application
by examining the values of tokens in the messages. For example, to select only event messages
reported by TMF software (a component of the NonStop Transaction Management Facility (TMF)
product), a filter would examine the token that contains the subsystem ID of the issuing subsystem
and then allow only those messages containing the TMF subsystem ID to pass.
You code a filter in the EMS filter language, compile the filter source file with the EMS filter compiler,
and load the resulting filter when you run the EMS consumer distributor. You can replace filters
online.
HP recommends that your application always use a filter when retrieving event messages. Otherwise,
the application receives all the event messages sent to the event log. You can use any of the
tokens contained in event messages to select the event messages that are returned to your
application. You can create filters that return only critical event messages, all messages associated
with a particular device, all messages with a certain event number, and so forth.
The EMS Manual provides information on how to code, compile, load, and replace filters.
Templates
Event-message templates are provided with TS/MP. These templates define the text used for displays
of event messages by the ViewPoint console application and other console devices and applications.
174 Event Management