search cancel

LOOKING FOR WARNING MECHANISM IN SYSVIEW/DB2 FOR PERCENTAGE REACHED

book

Article ID: 202362

calendar_today

Updated On:

Products

SYSVIEW Performance Management Option for DB2 for z/OS Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - SQL Performance Suite Insight Performance Monitor for DB2 UDB for z/OS

Issue/Introduction

WE'RE LOOKING FOR A MECHANISM IN SYSVIEW/DB2 TO WARN US WHEN PERCENTAGE OF MAXDBAT IS REACHED, OMEGAMON HAS ONE:

PK78018: KDP_MDBT_CRITICAL/WARNING SITUATION DESC NEEDS CORRECTION

KDP_MDBT_CRITICAL/WARNING situation in TEP has been changed to
trigger on number of DBAT approaching maximum from dsnzparm.
So, when the number of Database Active Threads is greater than a
threshold defined by the customer in TEP, the situation will
fire. The threshold is a percentage of MAXDBAT. For example
if MAXDBAT = 100 and the threshold is 80%, then 80 or more DBAT
threads will cause an alert to be generated.

Environment

Release : 20.0

Component : CA SYSVIEW Performance Management Option for DB2 for z/OS

Resolution

If you select option 0 Permanent Exception Definitions and then 1 Subsystem Exceptions.

Then Use F6 to add, then any of the first 7 options will give you the following: Exception Field Variables
Row 116-147/10186
Select field 1 using an "S". Then press Enter. DB2/IDB2 Field. Queued client conn TCPIP sockets closed - MAXDBAT QDSTNCQC