TMF Management Programming Manual (H06.05+)

SPI Programming Considerations for TMF
HP NonStop TMF Management Programming Manual—540140-002
3-10
Critical Events
Some TMF event messages contain extensible structured tokens providing information
for use by your application. In addition, some TMF event messages contain error lists.
Some of these error lists provide information for use by your application; others contain
information you should report to your service provider. The descriptions of individual
event messages in Section 6, Event Messages explain what to do with each error list.
Critical Events
Events reported by TMF are divided into two classes: critical and noncritical. Critical
events can have serious consequences, such as the loss of a device or the occurrence
of certain errors. Noncritical events are less serious, such as a counter exceeding a
threshold. The value of the token ZEMS-TKN-Emphasis indicates whether an event is
critical. If the value is ZSPI-VAL-True, the event is critical; if the value is ZSPI-VAL-
False, the event is not critical.
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, a filter would examine the
token that contains the subsystem ID of the issuing subsystem and then allow only
those messages containing TMF ID to pass.
You code a filter in the EMS filter language, compile the filter source file using the EMS
filter compiler, and load the resulting filter when you run the EMS consumer distributor.
You can replace filters online.
It is recommended that your application always use a filter when retrieving event
messages. Otherwise, the application will receive all the event messages sent to the
event log on the local system. You can use any of the tokens contained in event
messages to select which event messages will be 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 about how to code, compile, load, and replace
filters.
Templates and Labels
Event-message templates are provided with the TMF product. These define the text
used for displays of event messages by the ViewPoint console application and other
console devices and applications. Both source and compiled templates are provided.
You can modify the source templates and compile them again if you wish to customize
your messages.
The name of the TMF template object file is ZTMFTMPL; the source file is
STMFTMPL. For general information about DSM templates and instructions on how to
use and modify them, refer to the DSM Template Services Manual.