Batch Reporter

Getting started
The Batch Reporter enables you to generate reports that summarize and analyze historical performance data about your DB2® subsystems and applications.
Collecting data for reports
Before you can produce an OMEGAMON® for Db2 PE report, you must collect data from Db2 as input. The Db2 Instrumentation Facility Component (IFC) provides a trace facility that is used to record Db2 data and events.
Creating reports using commands
OMEGAMON for Db2 PE has a set of commands to create reports.
Creating reports with the Interactive Report Facility
The Interactive Report Facility (IRF) provides a dialog, though a series of panels, that guides you through the specifications for a report.
Using Statistics traces to get system overview information
The best way to get started with OMEGAMON for Db2 PE is to create a long Statistics trace report to get an overview of your Db2 system.
Using an Accounting report to analyze resource activities
The Accounting report shows how threads and applications perform in Db2.
Using Statistics and Accounting reports to identify exceptions
Exception reporting is a very effective way to identify performance problems. Exception reporting identifies Db2 threads and Statistics intervals with fields that contain values outside defined thresholds. This helps you manage performance objectives by highlighting problems in the DB2 subsystem, such as applications that are experiencing exceptional conditions or DB2 subsystem conditions that are causing thread performance problems.
Using SQL Activity reports to monitor SQL performance
SQL Activity reports provide detailed information about individual SQL statements in a plan or package. The SQL Activity report aggregates threads by a combination of OMEGAMON for Db2 PE identifiers. The SQL Activity trace shows details on a per thread basis.
Using Explain reports to monitor access paths
The OMEGAMON for Db2 Performance Expert Explain reports are built on the information that is supplied by the DB2 SQL Explain function and information taken from the system catalog tables. An Explain report provides information about the exact access path that is used by DB2 for any particular SQL statement and its effect on DB2 performance.
Locking Activity reports and traces
The locking activity provides various levels of detail about concurrency control within Db2 in the form of reports, traces, and a file data set.
I/O Activity reports
Db2 system performance is heavily influenced by the volume and speed of input activities and output activities. OMEGAMON for DB2 PE provides several summary and detail I/O Activity reports that you can use to analyze I/O activities.
Utility Activity reports
Many of the tasks of maintaining DB2 data, such as loading a table, copying a table space, or recovering a database to some previous point in time can be done using DB2 utilities. Utilities run as batch jobs under OS/390®. The use of utilities, such as REORG INDEX, can significantly affect DB2 performance. You can use Utility Activity reports and traces to examine the efficiency of Db2 utilities.
Record Trace reports
Record Trace reports show IFCID information as presented by DB2.
Housekeeping reports
These reports are not strictly performance reports. They present information about the Db2 system and user activity.
General Accounting information
This topic describes the Accounting report set and concepts in detail.
Creating effective Accounting reports
For a report to be effective it must deliver the information you need efficiently in terms of resources required to produce it, the volume of data produced, and the time it takes for you to interpret the report.
General Statistics information
Statistics reports and traces provide you with a way to analyze Db2 Statistics class 1 trace data.
Exception processing
Exception reporting identifies Accounting and Statistics records that contain fields with values that are outside a specified range. This helps you to recognize performance problems in the Db2 subsystem and in threads.
Reporting distributed data
OMEGAMON for Db2 Performance Expert can report activities that are associated with distributed work, where one Db2 subsystem accesses data from other DB2 subsystems.
Reporting data sharing information
Data sharing gives individual Db2 subsystems full access to databases that are on shared hard disk drives. The DB2 subsystems that share the data belong to a data sharing group and each subsystem is considered a member of the group.
Streamlining processing
Streamlining is the process of asking only for information in reports and traces that you really need.
Customizing functions
Customizing is the process of tailoring OMEGAMON for Db2 PE functions for specific needs, for example, specifying thresholds or modifying report layouts.
The Performance Database and the Performance Warehouse
OMEGAMON for Db2 Performance Expert performance data can be loaded into DB2 tables to build a performance database or a performance warehouse.
Generating input data for spreadsheets
With the Spreadsheet Input-Data Generator utility you can create input data for spreadsheets to ease DB2 performance analysis.
Using GROUP to improve Save data set performance
If you never require separate report entries for one or more OMEGAMON for Db2 PE identifiers, you can use GROUP to reduce the uniqueness of the key in the Save data. This can result in fewer reduced records in the Save data set, a smaller Save data set, and improved performance.
Comparing original authorization IDs with primary authorization IDs
This information explains the difference between original authorization ID and primary authorization ID.
Fields affected by roll-up during distributed and parallel tasks
The following table lists fields that are not reported by Accounting reports and traces if roll-up during distributed activity and parallel query tasks is active.
Using ACCOUNTING REDUCE subcommand options to balance performance and data set space
OMEGAMON for Db2 Performance Expert provides several commands for which the REDUCE subcommand and its options can be used to reduce the volume of data before the data is passed to subsequent other subcommands like REPORT and SAVE.
Troubleshooting empty reports
This topic lists and explains several reasons why your report might not contain any report data. Use this information as a guide to identify possible reasons, including inappropriate command parameters.