Chapter 8: Generating Commit Frequency Reports
This section contains the following topics:
Generate a Commit Frequency Report (see page 127) Commit Frequency Report Description (see page 128)
Generate a Commit Frequency Report
Use the Commit Frequency report to determine how often applications perform commits in relation to the number of updates made. This information can help you to monitor whether applications are adhering to local standards for database access. You can also see which plans are heavily updated within the scope of a single commit.
Follow these steps:
1. Select 1 (Process Log) from the CA Log Analyzer Main Menu and press Enter.
The Report Specification panel appears.
2. Select Commit Frequency and press Enter.
The Commit Report Options panel appears.
3. Complete the following fields:
■ Specify how much detail to include in the report using the Level of Detail field.
■ Specify the minimum number of updates without a commit to include in the report using the Commit Threshold field.
Note: A plan is included in the report when it makes updates that exceed the specified threshold within the scope of a single commit. For example, type 500 in this field to show plans that performed 500 or more updates before issuing a commit.
■ (Optional) Use the Plan Filters field to include or exclude specific plans from the report.
Press PF3 (End).
The Report Specification panel appears.
4. Press PF3 (End) again.
The Report Source Specifications panel appears.
Commit Frequency Report Description
128 User Guide
5. Enter the range of data to analyze. Optionally, you can also specify a source of log data other than the BSDS or DB2 catalog. For example, you can specify a log extract file that you previously created. (See the next step.)
Press PF3 (End).
The Output Specifications panel appears.
6. Specify a destination for the extract file and report.
Note: The extract file contains the log data that is analyzed for the report. You can save the extract file to a data set and then reuse it for subsequent analysis. Saving the file lets you avoid rereading the log when generating further reports on the same data.
Press PF3 (End).
The Report Submission panel appears.
7. Specify an execution mode and press Enter.
The report is generated and saved to the specified destination.
Commit Frequency Report Description
A Commit Frequency report shows how frequently commits are performed in relation to the number of updates made.
This report provides the following information, in the order shown:
■ The log processing range, which identifies the log range that was processed to generate the report. You specified the log range on the Report Source Specifications panel.
■ The report options that you selected on the Report Options panel.
■ The source options, which identify the DB2 log and table sources that were used to generate the report. You specified which sources to use on the Report Source Specifications panel.
■ The log extract summary, which identifies the log extract options and the Batch Processor statements that were used to generate the extract file. You specified a destination for the extract and its control file on the Process Log - Output
Specifications panel. These files are created whenever you use the BSDS or specific log data sets as the source of log data. You specified your batch execution
parameters on the Batch JCL Specification panel.
Chapter 8: Generating Commit Frequency Reports 129 This report section also provides the following information about the extract file:
PLA determined DB2 High log point
Identifies the highest log point that CA Log Analyzer has determined was written to the log when the extract file was generated.
PLR determined DB2 High log point
Identifies the highest log point the log reader has determined was written to the log when the extract file was generated.
High Processed DB2 log point
Identifies the log point of the highest UR that was encountered within the log processing range.
Note: This section appears only when you write the report to a data set or to SYSOUT. This section does not appear when the report is generated online for display at your terminal.
■ The log reporting options summary, which shows the Batch Processor statements that were used to generate the report.
Note: This section appears only when you write the report to a data set or to SYSOUT. This section does not appear when the report is generated online for display at your terminal.
■ The parmlib options, showing the highlevel.CDBAPARM(PLA) options that were in effect when you generated the report.
■ If you selected Summary as your level of detail on the Commit Report Options panel, the commit frequency summary appears next. This section shows the following information:
– A list of plans that exceeded the specified number of updates within a single commit scope. You specified this number in the Commit Threshold field on the Commit Report Options panel.
– For each plan, the average, maximum, and minimum number of updates that occurred within the scope of a single commit.
– The number of URIDs that were processed and the number of URIDs that exceeded the commit threshold.
■ If you selected Detail as your level of detail on the Commit Report Options panel, the detailed report section appears next. This section shows detailed information about each URID that exceeded the commit threshold. The report lists the URIDs from the highest number of updates to the lowest. The following information is shown for each UR:
– The associated plan that exceeded the commit threshold.
Commit Frequency Report Description
130 User Guide
– The number of updates that took place and the number of those updates that were performed to maintain RI.
– Detailed information about the UR.
■ The index appears at the end of the report. If multiple reports are generated, the index appears after the last report. The index identifies each report that has been generated, the subheadings for each report, and their corresponding page numbers.