Scenario 2: Defining Accounting and Statistics reports using an existing input data set

Suppose you are a database administrator for several OS/390® locations hosted on an MVS system. Users tell you that they have DB2® performance problems during online transaction processing on certain DB2 locations every day between 11 a.m. and 12 noon.

You decide to generate Accounting reports to determine if there is a DB2 problem. You also decide to generate a Statistics report to get an overview of system activity. You think that you might also need to analyze the data later using queries and rules of thumb, so you make sure that the performance data is transferred to the Performance Warehouse database.

To create the reports and transfer the data, you must:
  1. Create a REPORT step.
  2. Define the Accounting and Statistics reports.
  3. Run the process to generate reports and transfer data to the Performance Warehouse database.
  4. View and analyze the generated reports.

Scenario 1: Transferring performance data into the Performance Warehouse database describes how to work with process groups, processes and steps, how to run the process, and how to view the results. This scenario describes how to use Performance Warehouse to define the reports the DBA needs to analyze the problem. It assumes that you have an existing input data set containing the Accounting and Statistics performance records for the timeframe and DB2 locations in question. If this is not the case, proceed with Scenario 3: Collecting performance data for the generation of Accounting and Statistics reports.

To define the reports you must:
  1. Specify an input data set.
  2. Filter the performance records to produce meaningful results.
  3. Set up an Accounting report.
  4. Transfer data to the Performance Warehouse database.
  5. Set up a Statistics report.
You can perform these tasks on the following pages of the Performance Warehouse window:
  • Expert.
  • Report and Load.