V 4.2.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 and and IBM Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS; Reporting User’s Guide, SC19-2510-00, for Version 4.2.0

Content

  • Update 1: Modification to topic "Collecting report data with the Collect Report Data Batch program" (only ELAPSEDTIME stop criteria with GDGDATASET) in PK84461 (May 2009)
  • Update 2: Modification to "Chapter 3. Using OMEGAMON XE for DB2 PE reports" (April 2011)
  • Update 3: Placement of SYSIN statement corrected in several samples (June 2011)
  • Update 4: The following information was updated:
    The "Parts for Audit file data" table of section "Audit tables" in "Chapter 5. Advanced reporting concepts" (September 2011)
  • Update 5: The following information is updated:
    Section "Class 3 suspensions" in "Chapter 3. Using OMEGAMON XE for DB2 PE reports" (January 2012)

Update 5 (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"

Update 4 (September 2011)

The following information was modified:

Navigation: 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 (June 2011)

The following information was 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 2 (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.




Update 1: Modification to topic "Collecting report data with the Collect Report Data Batch program (only ELAPSEDTIME stop criteria with GDGDATASET) in PK84461 (May 2009)


The topic was updated as follows.


4.1.5 Collecting report data with the Collect Report Data Batch program

The new Collect Report Data Batch program allows for the collection of report data and postprocessing of collected report data by means of a batch job. This method provides a flexible way to automate the collection and postprocessing, thereby keeping the resource overhead minimized.

You can collect report data from a DB2 subsystem, a specified member of a data sharing group, or all members of a data sharing group. Collected report data is stored in a sequential data set or a Generation Data Group (GDG).

If a GDG is used, a user-specified job can be started to process collected report data automatically each time after a switch to a subsequent Generation Data Set (GDS) occurs. This method can be used to
continuously collect trace data from DB2 and to automate the postprocessing. For example, the contents of the GDG generations (the Generation Data Sets) can be used to automatically generate reports or
to load collected data into a Performance Database.

This method of collecting and postprocessing report data can be used as alternative to using System Management Facility (SMF) or Generalized Trace Facility (GTF) data sets if more flexibility regarding data
collection parameters and error handling and less resource overhead are required.

The commands and parameters that determine the collection and postprocessing of data must be specified in the SYSIN DD statement of the respective JCL, as outlined in the following syntax diagram. A
sample batch job can be found in data set prefix.TKO2SAMP(FPEZCRDJ).

               .-DSGLOBAL(N)-.                        
>>-SSID(ssid)--+-------------+--+-----------------+------------->
               '-DSGLOBAL(Y)-'  '-DSMEMBER(dsMbr)-'  

>--+-------------------------------------+---------------------->
   '-GDGDATASET(gdg)--+----------------+-'  
                      +-JOB(job)-------+    
                      +-VOLUME(volume)-+    
                      '-UNIT(unit)-----'    

                          .------------------------.  
   .-OPBUFSIZE(2048)---.  V .-ELAPSEDTIME(60)----. |  
>--+-------------------+----+-ELAPSEDTIME(secs)--+-+------------>
   '-OPBUFSIZE(opSize)-'    +-RECCOLLECTED(recs)-+    
                            '-TERMTHREADS(thds)--'    

   .----------------.  
   V                |  
>----TRACE('trace')-+------------------------------------------><




SSID
Specifies the DB2 subsystem ID ssid.

DSGLOBAL
Specifies whether to collect report data from all members of a data
sharing group.

N Specifies not to collect report data from all members. This is the
default.

Y Specifies to collect report data from all members. This setting is
ignored if the specified subsystem ID ssid is not a member of a
data sharing group.

DSMEMBER
Specifies the data sharing group member dsMbr from which to collect
report data. dsMbr can be located on a different LPAR.

GDGDATASET
Is optional. If specified, it determines that the trace data
collection will not terminate after a stop criteria is met, but the
output data set will be switched to the next generation of the
Generation Data Group (GDG), which means, to a subsequent Generation
Data Set (GDS). Specify the name of an existing GDG as gdg (the GDG
name, not a GDS name). Only ELAPSEDTIME may be used with
GDGDATASET to specify a stop criteria.

If specified, the JCL does not require an OUTPUT DD statement.

Use the PURGE operator command to stop CRD collection.

JOB
Is optional. If specified, job is executed after each switch to a
subsequent GDS. job must be the name of a started job.

This can be used to automatically process the data in a GDS, for
example, loading it into a Performance Database or generating
reports.

If you require the actual name of the Generation Data Set (GDS)
that was in use before the switch, you can specify the JCL symbol
&GDGDSN in the job's command stream, as in the following example:

//INPUTDD DD DSN=&GDGDSN,DISP=...

This method of using the JCL symbol ensures that the job is
synchronized with the proper generation of the GDG, in case new
generations are created faster than JES submits the specified job.

VOLUME
Is optional. A volume must be specified if a specified GDGDATASET
is not managed by SMS.

UNIT
Is optional. A unit must be specified if a specified GDGDATASET is
not managed by SMS.

OPBUFSIZE
Specifies the size (in KB) of the Online Performance (OP) buffer that
is used to buffer collected data.

2048
Is the default size.

opSize
Can be up to 16384 KB.

ELAPSEDTIME
Specifies one (of multiple) stop criteria for the data collect task.

60
Is the default duration (in seconds).

secs
Specifies the duration (in seconds).

RECCOLLECTED
Specifies one (of multiple) stop criteria for the data collect task.

recs
Specifies the maximum number of IFCID records to collect.

Not supported in combination with GDGDATASET.

TERMTHREADS
Specifies one (of multiple) stop criteria for the data collect task.

thds
Specifies the number of terminated threads after which data
collection stops.

Not supported in combination with GDGDATASET.

TRACE
Specifies the DB2 START TRACE command to collect data. The command
can start with a preceding dash (-). Do not use the DEST or SCOPE
subcommands unless a specific OP buffer should be used.

The following excerpt from a batch job shows how two START TRACE
commands are used to collect different trace classes and IFCIDs:


TRACE('START TRACE(PERFM) CLASS(30) IFCID(314) TDATA(CORRELATION,CPU)')
TRACE('START TRACE(AUDIT) CLASS(31) IFCID(140,83)')


Publication number

SC19-2510-00

Original publication date

2009/4/30

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

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

Software version:

4.2.0

Operating system(s):

z/OS

Software edition:

All Editions

Reference #:

7015876

Modified date:

2012-01-27

Translate my page

Machine Translation

Content navigation