Accounting trace overview
The best way to troubleshoot a poorly performing application is to understand where the time is actually spent and what DB2 resources are being used. DB2 traces provide these indicators, but you need to know how to interpret them and what the most efficient corrective actions are. If most of the time is spent using system CPU, what is the most likely culprit? If the problem is elapsed time, there are many types of suspensions and many of them have specific tuning steps to reduce the wait times.
This chapter discusses the ...
Get Subsystem and Transaction Monitoring and Tuning with DB2 11 for z/OS now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
