| Before you can run DB2 PM, you must have trace records produced by DB2 to feed into DB2 PM. Each DB2 PM report set requires certain traces to be started. For a synopsis of which traces to start for which information, refer to Table 24.3. Note that DB2 PM will not fail if you request a report for which no information or insufficient information is available. The report that DB2 PM generates, however, will be empty or incomplete. Table 24.3. Traces to Initiate for each DB2 PM Report Type | Report Type | Recommended Traces | Information Provided | | Accounting (General) | Accounting Class 1 | General accounting information | | Accounting Class 2 | In DB2 times | | Accounting Class 3 | Suspension times, out of DB2 times, system events | | Accounting Long | Accounting Class 1 | General accounting information | | Accounting Class 2 | In DB2 times | | Accounting Class 3 | Suspension times, out of DB2 times, system events | | Accounting Class 4 | Installation-defined | | Accounting Class 5 | Time spent processing IFI requests | | Accounting Class 7 | Entry or exit from DB2 event signaling for package and DBRM accounting | | Accounting Class 8 | Package wait time | | Audit | Audit Class 1 | Authorization failures | | Audit Class 2 | DCL | | Audit Class 3 | DDL | | Audit Class 4 | DML: First SELECT of audited table | | Audit Class 5 | DML: First UPDATE for audited tables | | Audit Class 6 | Bind | | Audit Class 7 | SET CURRENT SQLID | | Audit Class 8 | Utility executions | | Audit Class 9 | User-defined | | I/O Activity | Performance Class 4 | Buffer pool and EDM pool statistics | | Performance Class 5 | Logging and BSDS statistics | | Locking | Performance Class 6 | Lock suspensions , lock resumes, and lock contention information | | Record Trace | No traces specifically required | Formatted dump of all DB2 trace records in the given input data set | | SQL Trace | Accounting Class 1 | General accounting information | | Accounting Class 2 | In DB2 times | | Performance Class 2 | Aborts, commits, and thread- related data | | Performance Class 3 | Sort, AMS, plan, cursor, static SQL, and dynamic SQL statistics | | Performance Class 4 | Physical reads and writes | | Performance Class 6 | Lock suspensions, lock resumes, and lock contention information | | Performance Class 8 | Index access and sequential scan data | | Performance Class 13 | EDITPROC and VALIDPROC access | | Statistics | Statistics Class 1 | System and database services statistics | | Statistics Class 2 | Installation-defined | | Statistics Class 3 | Deadlock information | | Statistics Class 4 | DB2 exception condition | | Statistics Class 6 | DB2 storage information | | Summary | No traces specifically required | Basic summary of the steps taken by DB2 PM to produce other reports | | System Parameters | At least one type of trace | Installation parameters (DSNZPARMs) | | Transit Time | Performance Class 1 | Background events | | Performance Class 2 | Aborts, commits, and thread-related data | | Performance Class 3 | Sort, AMS, plans, cursor, static SQL, and dynamic SQL statistics | | Performance Class 4 | Physical reads and writes | | Performance Class 6 | Lock suspensions, lock resumes, and lock contention information | | Performance Class 10 | Optimizer and bind statistics | | Performance Class 13 | EDITPROC and VALIDPROC access |
Be sure to start the appropriate traces as outlined in Table 24.3 before running DB2 PM. To run a report indicated in the left column, you should start the recommended traces to get useful information from DB2 PM. If a particular trace is not started, the DB2 PM report still prints, but you do not get all the information the report can provide. Failure to start all these traces may result in some report values being left blank or listed as N/C. You should develop standards for the production of DB2 PM reports to monitor the performance of DB2 and its applications at your shop. Use the chart in Table 24.4 as a guideline for establishing a regular DB2 PM reporting cycle. You can modify and augment this table based on your shop's DB2 performance monitoring requirements and standards. Table 24.4. DB2 PM Monitoring Reference | Resource to Monitor | DB2 PM Report | Frequency | | DB2 Subsystem | Statistics Summary | Weekly | | Statistics Detail | As needed | | I/O Activity Summary | Monthly | | I/O Buffer Pool Activity Detail | As needed | | I/O EDM Pool Activity Detail | As needed | | I/O Log Manager Activity Detail | As needed | | System Parameters | When DB2 is recycled | | Audit Summary | Weekly | | DB2 Applications | Accounting Short | Daily | | Accounting Long | As needed | | Audited DML Access | Weekly | | Lock Contention | As needed | | Lock Suspension | As needed | | Exception | Transit Time report solving | Problem Monitoring | | SQL Trace | Problem solving | | Record Trace | DB2 or DB2 PM problem solving | | Summary report | DB2 PM problem solving | | Lock Contention | Problem solving | | Lock Suspension | Problem solving | | Security | Audit Authorization Failures | Weekly | | Audit Authorization Control | Weekly | | Audit Authorization Change | Weekly | | Audited DDL Access | Weekly | | Audited DML Access | Weekly | | Audit Utility Access | Weekly |
Some performance monitoring software from other vendors can provide the same batch reporting functionality as DB2 PM. You might want to reconsider whether you need DB2 PM, because DB2 PM is not as mature an online performance monitor as other products, or maybe your company has standardized on a monitoring family of products (such as MainView or Omegamom) that monitor not just DB2, but also CICS, IMS, z/OS, and other resources. Before you decide to avoid DB2 PM in favor of the batch performance monitoring provided by another tool, consider the following: -
When performance problems that require IBM intervention persist, IBM often requests that you run a performance trace and generate DB2 PM reports for the trace. To be sure that IBM will accept reports generated by the third-party tool, compare the output from the vendor tool to the output from DB2 PM. If the reports are almost identical, you usually will not have a problem. To be absolutely sure, ask your IBM support center. -
DB2 PM is an industry standard for batch performance monitoring. Taking classes on performance monitoring is easier when the monitoring is based on DB2 PM reports. Classes offered by IBM (and others) on DB2 performance usually use DB2 PM reports as examples. As such, having access to DB2 PM is helpful for students. Additionally, if you need to add staff, DB2 PM trained personnel can be easier to find. -
DB2 PM may be updated for new releases of DB2 more quickly than third-party monitoring tools because IBM is closer than anyone else to the code of DB2. If you need to migrate to new versions of DB2 rapidly , DB2 PM may be the only monitor positioned for the new release at the same time as your shop. |
