Exclude a small subset of CICS transactions in Application Exception definition within Sysview for Db2

Products

• SYSVIEW Performance Management Option for DB2 for z/OS

Issue/Introduction

A defined Sysview Performance Management Option for Db2 for z/OS (IDB2) Application Exception for long running CICS transactions has set
CPU limit of 100 seconds per unit of work for all CICS transactions. It is observed that there are few genuine CICS transactions which can
exceed 100 CPU seconds based on their business requirements. But majority of CICS transactions use CPU which is well below 100 seconds per unit of work.
This has raised the requirement to exclude a small list of CICS transactions in this exception definition. Is there any way, by which to exclude a small subset
of CICS transactions in Application Exception definition?

Resolution

The Exception System allows for application exceptions to be created with filters for Db2 subsystem id, connection name, plan name, and connection type.
You can use connection type 12 to monitor only CICS threads. To exclude a subset of these CICS threads, the recommendation would be to assign this
subset to a CICS RCT entry with it's own unique plan name, and then write a second application exception using this plan name as a filter criteria.
Then raise the CPU time limit on this exception, to allow for the fact that they normally use more CPU then other CICS transactions.