V 5.1.0: Update to the Reporting User’s Guide of IBM Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS and IBM Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS

Manual


Abstract

This document updates the IBM® Tivoli® OMEGAMON® XE for DB2® Performance Expert on z/OS® ; IBM Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS Version 5.1.0: Reporting User’s Guide, SH12-6927-01.

Content

  • Update 1 (April 2011): The information in the following chapter is updated:
    "Chapter 3. Using OMEGAMON XE for DB2 PE reports"
  • Update 2 (June 2011): The following information is updated:
    Placement of SYSIN statement corrected in several samples
  • Update 3 (August 2011): The following information is updated:
    "Example of ordering by activity name: ORDER (ACTNAME)" in "Chapter 5. Advanced reporting concepts"
  • Update 4 (September 2011): The following information is updated:
    The "Parts for Audit file data" table of section "Audit tables" in "Chapter 5. Advanced reporting concepts"
  • Update 5 in PM47871 (October 2011): The following information is updated: IFCID 316 and 401 are added to
    section "The Performance Database and the Performance Warehouse" and "Record Trace tables" in "Chapter 5. Advanced reporting concepts"
  • Update 6 (January 2012): The following information is updated:
    Section "Class 3 suspensions" in "Chapter 3. Using OMEGAMON XE for DB2 PE reports"
  • Update 7 in PM48395 and general update (February 2012): The following information is updated:
    Section "Ordering by Package or DBRM: ORDER (PACKAGE)" and "Example of ordering by activity name: ORDER (ACTNAME)" in "Chapter 5. Advanced reporting concepts"
  • Update 8 in PM55120 (April 2012): The following information is updated:
    Section "Configuring a collect task" (Trace Configuration window) in "Chapter 3. Collecting data for reports"
  • Update 9* in PM73732 (December 2012):
    Information for Accelerator data and the new Spreadsheet Input-Data Generator utility has been added to the information:
    • Chapter 16. "General Accounting information" -> Functions and utilities of the Accounting report set
    • Chapter 18. "General Statistics information" -> Functions and utilities of the Statistics report set
    • Chapter 21. The Performance Database and the Performance Warehouse -> "Data structure" ->"Accounting tables"
    • Chapter 21. The Performance Database and the Performance Warehouse -> "Data structure" -> "Statistics tables"
    • Chapter 25. "Generating input data for spreadsheets" (updated: 20 December 2012)
  • Update 10* in PM84930 (May 2013):
    The section "Example of an OMEGAMON XE for DB2 PE command string" has been updated in Chapter 4. "Creating reports with OMEGAMON XE for DB2 PE commands".
  • Update 11* in PM96290 (October 2013):
    The following information has been updated:
    Chapter 25. "Generating input data for spreadsheets".

*Note: The chapter structure in the updated PDF attachments of this document does not reflect the chapter structure of the existing book.


Update 11* in PM96290 (October 2013)
The following information has been updated:

*Note: The chapter structure in the updated PDF attachments of this document does not reflect the chapter structure of the existing book.

Update 10* in PM84930 (May 2013)
The following information has been updated:


*Note: The chapter structure in the updated PDF attachments of this document does not reflect the chapter structure of the existing book.


Update 9* in PM73732 (December 2012)

The following information has been updated to include accelerator data and the new Spreadsheet Input-Data Generator utility:


*Note: The chapter structure in the updated PDF attachments of this document does not reflect the chapter structure of the existing book.

Update 8 in PM55120 (April 2012)

The following information is updated:
The Trace Configuration window has been modified in section "Configuring a collect task":
Chap3_Configuring a collect task.pdfChap3_Configuring a collect task.pdf

Update 7 in PM48395 and general update (February 2012)

The following information is updated:
Navigation: Double-click:

  1. "Chapter 5. Advanced reporting concepts"
  2. "Accounting report set"
  3. "Creating effective Accounting reports"
  4. "ORDER processing"
  5. "Example of ordering by activity name: ORDER (ACTNAME)"

The following information is updated:
  • "Package SQL Activity" and "Package Locking Activity" have been added to the list of package report blocks in section "Ordering by Package or DBRM: ORDER (PACKAGE)" .
  • The note on average calculation in section “Example of ordering by activity name: ORDER (ACTNAME)” is revised.

Chap5_Order processing examples.pdfChap5_Order processing examples.pdf

Update 6 (January 2012)

The following information is updated:
Navigation: Double-click:

  1. "Chapter 3. Using OMEGAMON XE for DB2 PE reports"
  2. "Using an Accounting report to analyze resource activities"
  3. "Interpreting the Accounting trace report and applying rules of thumb"
  4. "Class 3 suspensions"
Chap3_Class 3 suspensions.pdf

Update 5 in PM47871 (October 2011)

The following information is modified:

Navigation in current publication: Double-click:

  1. "Chapter 5. Advanced reporting concepts"
  2. "The Performance Database and the Performance Warehouse"
  3. "Record trace tables"

Performance_DB_and_Performance_Warehouse.pdf

Update 4 (September 2011)

The following information is modified:

Navigation in current publication: Double-click:

  1. "Chapter 5. Advanced reporting concepts"
  2. "The Performance Database and the Performance Warehouse"
  3. "Database structure"
  4. "Audit tables"
  5. Table "Parts for Audit file data"

The "Bind Repeating Data" type was added to the table "Parts for Audit file data":

Update 3 (August 2011)

The following information is modified:


"Chapter 5. Advanced reporting concepts":
The new OMEGAMON XE for DB2 PE identifier ACTNAME of the ORDER subcommand was added.

Navigation in current publication: Double-click:

  1. "Chapter 5. Advanced reporting concepts"
  2. "Accounting report set"
  3. "Creating effective Accounting reports"
  4. "ORDER processing"
  5. "Example of ordering by activity name: ORDER (ACTNAME)"

Example of ordering by activity name: ORDER (ACTNAME)
This example shows how to order an Accounting report by activity name.
If you want to use ORDER (ACTNAME), you should consider the following:
  • ACTNAME cannot be combined with other OMEGAMON XE for DB2 PE identifiers in the ORDER subcommand.
  • ORDER (ACTNAME) is only allowed for reports that are created from input trace specified with //INPUTDD.
  • If you use the RESTORE subcommand, you cannot order by activity name in the subsequent REPORT subcommands.

The following command orders an Accounting report by activity name.
...
ACCOUNTING
REPORT
ORDER (ACTNAME) ...

To identify the real number of stored procedures (SP) or user-defined functions (UDF) instead of the number of packages used, you must include trace collection of IFCID 233 (Start/Stop for each SP or UDF) in your input trace data. Stored procedures and user-defined functions are determined and can be counted if IFCID 233 is found. Subprograms called by these routines and functions are not taken into account for the number of occurrences.

Note: If an IFCID 233 is not available for each SP or UDF, all packages of the same activity type and activity name are counted as separate occurrences and the sum is divided by the number of occurrences to calculate the average value.

Sample workload with two different SPs and subprograms
Table 13 shows a workload of six threads with stored procedures (SP) and subprograms. In this sample workload IFCID 233 is written for each SP execution. Package SP-A has the activity name ACTNAME-A. Package SP-B has the activity name ACTNAME-B. Packages PKG1, PKG2, or PKG3 are linked by SP-A or SP-B that is why they inherit their activity names.


Comparison of Accounting report types based on the above sample workload:
The report layout depends on the OMEGAMON XE for DB2 PE subcommand option of ORDER specified for producing an Accounting report.
If the DB2 subsystem parameter ACCUMACC is used, the report layout provided with DB2 10 differs from the report layout provided with a DB2 version prior to DB2 10.
Each report is based on the sample workload in Table 13.

Subcommand ORDER (PLANNAME)
The following report is a typical Accounting report ordered by various identifiers on plan level with their packages underneath. It is produced if you specify, for example, ORDER (PLANNAME):

Subcommand ORDER (PACKAGE)
The following sample shows a report:
  • Ordered by package
  • Average for each package
  • Average cross plan
  • Occurrences are equal to the number of package sections found in all plans

The following Accounting report is ordered by package, which reports on package level cross thread/plan usage. It is produced if you specify, for example, ORDER (PACKAGE):

Subcommand ORDER (ACTNAME) with IFCID 233 available for each stored procedure
The following sample shows a report:
  • Ordered by activity name
  • Average for each SP
  • Includes all processing subprograms under SP
  • Occurrences are equal to the number of SP calls

The following Accounting report is ordered by activity name (stored procedure) where all activities (subprograms) underneath the stored procedure are included in the SP average values. It is produced if you specify ORDER (ACTNAME) and your input trace data includes IFCID 233 for each SP:

Note: Explanation for the above sample:
  • Under SP-A with the activity name ACTNAME_A the average execution of SP-A is shown which includes all PKG1, PKG2, and PKG3 workloads associated with this stored procedure.
  • Under SP-B with the activity name ACTNAME_B the average execution of SP-B is shown which includes all PKG1 workloads associated with this stored procedure.

Subcommand ORDER (ACTNAME) without IFCID 233 in a DB2 trace
The following sample shows a report:
  • Ordered by activity name
  • Average for each SP
  • Includes all processing under SP
  • Occurrences are equal to the number of package sections, including SP as a package

The following Accounting report is ordered by activity name (stored procedure) where all activities (subprograms) underneath the SP are included. The average values shown represent the aggregation of all packages including SPs executed within an SP. However, all subprograms are counted as separate occurrences because no IFCIDs 233 were found by the reporting program:

Note: Explanation for the above sample:
  • Under SP-A with the activity name ACTNAME_A the average of the aggregation for each package section executed under SP-A (ACTNAME_A, PKG1, PKG2, PKG3) is shown.
  • Under SP-B with the activity name ACTNAME_B the average of the aggregation for each package section executed under SP-B (ACTNAME_B and PKG1) is shown.

The impact of the DB2 subsystem parameter ACCUMACC:
The DB2 subsystem parameter ACCUMACC determines whether DB2 Accounting data is to be accumulated by the user for DDF and RRSAF threads. If ACCUMACC is greater than 0, the threads which relate to the same Accounting accumulation identifiers (defined by the aggregation field ACCUMUID) are aggregated into one Accounting trace record (3, 239). For DB2 versions prior to version 10 all packages of these accumulated threads are reported into one package section. As a result you lose the granularity for each package and you cannot:
  • Distinguish between SP and called subprograms.
  • Determine which thread has executed which SP or package.

Starting with DB2 10 reports show the first 24 different packages or SPs of the accumulated threads in separate data sections (239) and only if there are more than 24 packages, all the remaining packages will be accumulated into the 25th data section.
For more information on DB2 subsystem parameters refer to the DB2 information center.



Update 2 (June 2011)
Placement of SYSIN statement corrected in several samples:

The following information is modified:
- Chapter 2. Generating OMEGAMON XE for DB2 PE reports

"Figure 13. Specifying a job stream using ISPF/PDF editor" in section "Example of an OMEGAMON XE for DB2 PE command string":


- Chapter 3. Using OMEGAMON XE for DB2 PE reports

"Figure 26. Specifying a job stream using ISPF/PDF editor" in section "Creating a Statistics trace report":


"Figure 27. Specifying a job stream using ISPF/PDF editor" in section "Creating a short Accounting report":


"Figure 29. Specifying a job stream using ISPF/PDF editor" in section "Interpreting the Accounting report and making changes":


"Figure 37. SQL Activity job stream using ISPF/PDF editor" in section "Creating an OMEGAMON XE for DB2 PE SQL Activity trace":


- Chapter 4. Other OMEGAMON XE for DB2 PE reports

"Figure 65. Record trace job stream using ISPF/PDF editor" in section "Creating an OMEGAMON XE for DB2 PE Record Trace report":




Update 1 (April 2011)

The following information was modified:
- "Chapter 3. Using OMEGAMON XE for DB2 PE reports"

"Collecting Statistics data with a DB2 trace" in section "Using Statistics traces to get system overview information"

Collecting Statistics data with a DB2 trace
Use the Performance Expert Client to configure and start a DB2 trace to collect
DB2 Statistics data during a 24-hour period.
About this task
To do this, start the Performance Expert Client:

  1. On the menu bar of the System Overview window, click Tools -->Performance Warehouse - Expert to open the Performance Warehouse window.
  2. On the Performance Warehouse window, select the Trace on z/OS tab.
  3. Open the folders to connect to the z/OS subsystem.
  4. Switch to your private group. If not available, right-click the Process Groups node to create your private copy.
  5. Expand the public tree
  6. Copy the CRD (collect report data) process template from the Public process groups to a process group of your own.
  7. Expand your private group tree.
  8. Double-click the CRD step to open the CRD Step Properties window.
  9. Open the Options page and change the following option categories:
    • For Output data set, type an output data set name and select Append or Overwrite.
    • For Data, clear the Statistics check box. Specify which IFCIDs you want to collect. The IFCIDs associated with this trace are displayed and highlighted. Only the highlighted IFCIDs are collected in the trace. Here you can, for example, choose not to include buffer pool statistics at data set level.
    • For Stop, specify the criteria for the data collection. Select the Elapsed time check box and specify a time of 24:00:00.
    • Click OK to save the configuration of the CRD step.
  10. When finished, right-click the CRD process and select Execute to open the Performance Warehouse Process Scheduler window to define a schedule for the selected process.
  11. Select the Execute once, immediately to run the process once.
  12. Click Finish to start the trace.


"Collecting Accounting data with a DB2 trace" in section "Using an Accounting report to analyze resource activities":

Collecting Accounting data with a DB2 trace
Use the Performance Expert Client to configure and start a DB2 trace to collect
DB2 Accounting data during a 24-hour period.
About this task
To do this, start the Performance Expert Client:
  1. 1. On the menu bar of the System Overview window, click Tools -->Performance Warehouse - Expert to open the Performance Warehouse window.
  2. On the Performance Warehouse window, select the Trace on z/OS tab.
  3. Open the folders to connect to the z/OS subsystem.
  4. Switch to your private group. If not available, right-click the Process Groups node to create your private copy.
  5. Expand the public tree
  6. Copy the CRD (collect report data) process template from the Public process groups to a process group of your own.
  7. Expand your private group tree.
  8. Double-click the CRD step to open the CRD Step Properties window.
  9. Open the Options page and change the following option categories:
    • For Output data set, type an output data set name and select Append or Overwrite.
    • For Data, clear the Accounting check box. Specify which IFCIDs you want to collect. The IFCIDs associated with this trace are displayed and highlighted. Only the highlighted IFCIDs are collected in the trace. Here you can, for example, choose not to include buffer pool accounting at data set level.
    • For Stop, specify the criteria for the data collection.
    • Select the Elapsed time check box and specify a time of 24:00:00.
    • Click OK to save the configuration of the CRD step.
  10. When finished, right-click the CRD process and select Execute to open the Performance Warehouse Process Scheduler window to define a schedule for the selected process.
  11. Select the Execute once, immediately to run the process once.
  12. Click Finish to start the trace.


Related information

Information Management
Tivoli Software Information

Publication number

SH12-6927-01

Copyright date

1985, 2011

Original publication date

2011/3/8

Product Alias/Synonym

OMEGAMON XE for DB2 PE
OMEGAMON XE for DB2 PM

Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 Tools for z/OS
IBM Tivoli OMEGAMON XE for DB2 PE / PM / BPA

Software version:

5.1.0

Operating system(s):

z/OS

Reference #:

7021212

Modified date:

2013-11-04

Translate my page

Machine Translation

Content navigation