Tracing "other DB Time" contributors

book

Article ID: 14930

calendar_today

Updated On:

Products

CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS

Issue/Introduction



What are the traces/reports or other panels  needed to look at contributors to "other DB2 time" shown  on Response Time History (Panel DBGSDISH)? 

Environment

Release:
Component: CIDB

Resolution

BTACTSML or BTACTTRL requests report Other DB2 Time. Other DB2 time shows the average thread elapsed time in DB2 that is not included in TCB time or in any of the suspension categories. The most common contributors to other DB2 time are MVS paging and Processor wait time "Other DB2" time is often a though one to debug. It is basically any left over time that is not attributable to any other CPU or suspend time that DB2 accounts for. The only two things you can try with CA-Insight is to start either an SQLTRACE or a hierarchical probe to trace the applications in detail. The other thing is to use the option1.6.1.4 from the main Menu(Address Space Tasks) to see if you notice the TCBs in any particular wait state.

STROBE can be used to determine what is causing the task delays.