OSI/FTAM Configuration and Management Manual

Monitoring FTAM Performance

OSI/FTAM Configuration and Management Manual—421944-001

5-11

Filtering Event Messages

As described in Section 2, FTAM Management Environment, a filter is a program you

can write to select the event messages that you want to display, route, or process.

Filtering strategies involve sorting the collected messages collected by EMS into logical

groupings to which you can refer. Although the subsystem-specific tokens in APLMGR

and FTAM event messages are not documented for customer use, you can filter on

tokens in the event-message header, which are common to all subsystems. These header

tokens, described in the EMS Manual, include the subsystem ID, which identifies the

subsystem that generated the event message, and the EMPHASIS token, which

identifies critical events.

Consider the following strategies for filtering Tandem FTAM event messages:

•

Filter messages with the APLMGR and the FTAM subsystem IDs to separate FTAM

product-related events from other events occurring on your system.

•

Filter messages by both subsystem IDs and a value of TRUE for the EMPHASIS

token to separate all FTAM and APLMGR critical events messages from the rest.

Appendix B, FTAM EMS Filters

, presents sample filters that implement these two

strategies. To create filters that select messages of certain types, you can use or modify

the example filters described and provided with the Tandem FTAM product; these are

installed, by default, in the ZOSIFTAM subvolume. After a filter is compiled, direct the

distributor to load the filter by including a filter parameter and specifying the name of

the file containing the filter. For details on the actual command sequences for creating

subsystem-specific filters, see the EMS Manual.