Q ON MONITORING LIFETIME OF DB2 TRANSACTIONS

book

Article ID: 140440

calendar_today

Updated On:

Products

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

Issue/Introduction

Customer explained their request:
 
A need has come up for us to monitor the lifetime of a DB2 transaction--through     the
user name. 
 
On SYSVIEW for DB2 we found an option     "0 Permanent Exception Definitions"    "3 
Application Exceptions (Includes SQL based)"--the metric below I believe could   meet
our need--but it does not allow specifying the user:
 
INACT  **** ********  SQL  Long running SQL: PLAN=&PLANNAM, AUTH=&AUTHIDX,
           ********      CONN=&CONNNAM, CORR=&CORRELATION, Resp=&VALUEXX
 
We need a suggestion for the best way to accomplish this monitoring--either  by using
SYSVIEW for DB2 or by using SYSVIEW itself.
                                                        

Cause

-

Environment

OS : z/OS

Release : 20.0

Component : CA Insight Database Performance Monitor for DB for z/OS

Resolution

Our product specialist offered to customer an alternative solution:


The following exception:


INACT  **** ********  SQL  Long running SQL: PLAN=&PLANNAM, AUTH=&AUTHIDX,

           ********      CONN=&CONNNAM, CORR=&CORRELATION, Resp=&VALUEXX


does not allow you to filter by USERID as you already noticed.


-


IDB2 gives you the option to use IQL (Insight Query Language) type exceptions--which 

may give you the ability to implement this.