Monitoring Menu Options › Monitoring Submenus › Hierarchy Rules for Monitored Entries

Hierarchy Rules for Monitored Entries

It is important to know the priorities CA InterTest for CICS observes if more than one entry in the Monitoring Table applies to the same program.

• A specific or generic program entry overrides a transaction entry, a terminal entry, and an .ALL specification
• A transaction entry overrides a terminal entry and an .ALL specification
• A terminal entry (specific or generic) overrides an .ALL specification

Example

Suppose you specify monitoring options for program ABC1 and different options for transaction TRN1. ABC1 executes as part of that transaction. When ABC1 executes, the options specified for ABC1 override the options specified for TRN1. Similarly, it is important to understand the priorities CA InterTest for CICS observes when a program, transaction, or terminal is specifically and generically declared for monitoring. A specific entry overrides a generic entry except when you request Status Display. In that case, the generic specification takes precedence.

Suppose you specify monitoring options for program ABC1 and different monitoring options for program ABC*. The options specified for ABC* affect all programs whose names begin with ABC except for program ABC1 (and any other programs beginning with ABC that have their own entries in the Monitoring Table). Monitoring for ABC1 is controlled by the specific entry for that program. However, if you request a Status Display for program ABC*, you get monitoring status reports for all programs that begin with ABC, including program ABC1 that has a separate Monitoring Table entry.