V5.1.0: Update to the Report Command Reference manual of IBM Tivoli OMEGAMON for DB2 Performance Expert and Performance Monitor on z/OS

Manual


Abstract

This document updates the IBM® Tivoli® OMEGAMON for DB2® Performance Expert and Performance Monitor on z/OS Report Command Reference manual, SH12-6922-00, for Version 5.1.0.

Content

This manual includes the following updates:

  • Update 1: Added ACTNAME in Table 7 'OMEGAMON XE for DB2 PE identifiers used with ORDER subcommand option' in PM34995 (July 2011)
  • Update 2: Added an explanation of a dependency between the two commands AUDIT REPORT LEVEL(SUMMARY) and AUDIT REPORT LEVEL(DETAIL) (October 2011)
  • Update 3: Added a new DATATYPE to the ACCOUNTING command with SAVE subcommand in PM49684 (November 2011)
  • Update 4: Modified two value descriptions of CONNTYPE in Chapter 2 (December 2011)
  • Update 5: Added option ACCEL to LAYOUT subcommand option (January 2012)
  • Update 6: Added FILE DATATYPE(ACCEL) option for the ACCOUNTING command for PM73732 (December 2012)
  • Update 7: Added usage information about the new Spreadsheet Input Data Generator utility for PM73732 (December 2012)
  • Update 8: Changes to the 'ACCOUNTING command with REPORT subcommand' topic in Chapter 7 for PM73547 (January 2013)

Update 1: Added ACTNAME in Table 7 'OMEGAMON XE for DB2 PE identifiers used with ORDER subcommand option' in PM34995 (July 2011)




Update 2: Added a note about a dependency between the two commands AUDIT REPORT LEVEL(SUMMARY) and AUDIT REPORT LEVEL(DETAIL) (October 2011)

There is a dependency between the two commands AUDIT REPORT LEVEL(SUMMARY) and AUDIT REPORT LEVEL(DETAIL). If you request a SUMMARY report and a DETAIL report for the same audit TYPE, then first specify the DETAIL report and then the SUMMARY report in order to receive meaningful data in the SUMMARY report.
If you request a SUMMARY report without a DETAIL report, then there is no dependency and the SUMMARY report delivers valuable results.

Update 3: Added DATATYPE ACCEL to the ACCOUNTING command with SAVE subcommand (November 2011)


Syntax of the SAVE subcommand


Subcommand options

The syntax diagram shows the options that are available with this subcommand. See OMEGAMON XE for DB2 PE subcommand options for comprehensive descriptions of these options. The following list gives additional or specific descriptions of selected options, where appropriate.

DATATYPE

    Specifies which data types are to be written to the VSAM data set with each record. By default, if DATATYPE is not specified, or if DATATYPE() is specified (without keywords), all data types are written to the reduced data set.

    This subcommand option lets you improve the system performance while the VSAM data set is generated by explicitly specifying only the required data types. If performance is not critical, you can safely ignore this subcommand option. Use one or more of the following keywords to specify the required data types.

    Note: Note that a later restore of partially saved data does not reconstruct the unsaved data types.
    GENERAL

      General performance data. Always required for a save data set. Note that the GENERAL keyword needs to be specified explicitly.
    BP
      Buffer pool performance data
    GBP
      Group buffer pool performance data
    DDF
      Distributed Data Facility (DDF) data
    RLF
      Resource Limit Facility (RLF) data
    PACKAGE
      Package execution data
    ACCEL
      Accelerator data

Update 4: Modified two value descriptions of CONNTYPE in Chapter 2 (December 2011)

The following value descriptions of CONNTYPE are modified in Chapter 2 'OMEGAMON XE for DB2 PE identifiers', 'Identifiers', 'CONNTYPE':
DB2 PRIV - DB2 private protocol
DLI-BTCH - DL/I batch

Update 5: Added option ACCEL to LAYOUT subcommand option (January 2012)


LAYOUT subcommand option

The LAYOUT subcommand option specifies the name of a report layout.

Usage

You can select the layout of Accounting and Statistics model reports and traces.

Usage notes

  • If none of them suit the requirements at your site, you can tailor your own layouts using the User-Tailored Reporting feature (UTR). For details refer to the Reporting User's Guide.
  • Migration layouts help you identify data that was previously shown in the reports of the OMEGAMON® Historical Reporter.
Options
You can specify one of the supplied layouts or one that you have previously tailored:
SHORT
    Provides a short layout. SHORT is used by default.
    Note: If a report does not contain the details that you are looking for (such as thread-related data), run the job again using the LAYOUT subcommand option LONG. You can also use other functions such as Record Trace and SQL Activity to find detailed DB2® trace data.
LONG
    Provides detailed thread-related data.
ACCEL
    Accounting: Provides detailed thread-related Accelerator activity data.
    Statistics: Provides detailed system-related Accelerator activity data.
migration layouts user-defined layouts
    You can customize your own report layouts by specifying which blocks of data and which fields within the blocks are included, and their relative order. To adapt the reports according to your requirements, you use user-tailored reporting (UTR). With UTR, you can control the volume, contents, and layout of Statistics traces and reports.

    Update 6: Added FILE DATATYPE(ACCEL) option for the ACCOUNTING command for PM73732 (December 2012)


    ACCOUNTING command with FILE subcommand

    This section describes the ACCOUNTING command with the FILE subcommand.

    Usage
    Use the FILE subcommand to format unreduced DB2® data and store it in
    sequential data sets suitable for use by the DB2 load utility.

    Usage notes

    • In the case of CP parallelism, the logical Accounting record (aggregation of all
      the activity within the thread) is stored in the data set.
    • The records can be placed in DB2 tables, and you can produce reports by using
      a reporting facility such as Query Management Facility (QMF™).

    Syntax of the FILE subcommand

    Subcommand options
    The syntax diagram shows the options that are available with this subcommand.
    See OMEGAMON® XE for DB2 PE subcommand options for comprehensive
    descriptions of these options. The following list gives additional or specific
    descriptions of selected options, where appropriate.

    FROM/TO
    Limits the range of records included in the data set by date and time.
    For details, see FROM/TO subcommand options.
    If you are reducing data, the times specified in REDUCE affect the data
    available for filing.

    EXCEPTION
    NOEXCEPTION
    Specify EXCEPTION if you want to include only those file entries with values
    outside the user-specified limits. Otherwise, all records are included.
    If you use this option, your JCL must contain a valid DD definition for the
    ddname EXCPTDD. For more information about required ddnames, see
    Sample JCL for requesting Accounting functions.

    DATATYPE
    Specifies which data types are to be written to the FILE data set specified in
    the DDNAME subcommand option. By default, if DATATYPE is not specified,
    or if DATATYPE() is specified (without keywords), all data types are written.
    This subcommand option lets you improve the system performance while the
    data set is generated by explicitly specifying only the required data types. If
    performance is not critical, you can safely ignore this subcommand option. Use
    one or more of the following keywords to specify the required data types.

    GENERAL
    General performance data
    BP
    Buffer pool performance data
    GBP
    Group buffer pool performance data
    DDF
    Distributed Data Facility (DDF) data
    PACKAGE
    Package execution data
    ACCEL
    Accelerator data


    Update 7: Added usage information about the new Spreadsheet Input Data Generator utility for PM73732 (December 2012)


    SPREADSHEETDD subcommand option

    The SPREADSHEETDD subcommand is used to write locking and statistics related DB2® data to a specified data set.

    Usage

    The SPREADSHEETDD subcommand option can be used to write locking and statistics related DB2 data to a specified data set in a format that can be imported by common spreadsheet programs. This subcommand option is only applicable to the REPORT subcommand of the LOCKING command and to the FILE subcommand of the STATISTICS command.

    Instead of this subcommand and for statistics and accounting only, you can use the Spreadsheet Input Data Generator utility to create CSV (comma-separated value) data for spreadsheet programs as described in Reporting User's Guide (http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.xe.pe_db2.doc_5.1.1/ko2ru/ko2ru_about.htm).


    ACCOUNTING command with SAVE subcommand

    This section describes the ACCOUNTING command with the SAVE subcommand.

    Usage
    Use the SAVE subcommand to produce a VSAM data set containing reduced records. After the data has been saved, you can:

    • Convert the save files to sequential data sets by using the save-file utility and load it to DB2® for subsequent use.
    • Restore and combine it with newly reduced data to produce long-term reports.
    • Restore it and use it in later reporting.

    You can also use the converted SAVE data sets to generate CSV (comma-separated value) input-data. This CSV data can then be transferred to workstations and imported into spreadsheets to improve DB2 performance analysis using graphical representations or pivot tables. For more information refer to Reporting User's Guide (http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.xe.pe_db2.doc_5.1.1/ko2ru/ko2ru_about.htm).


    ACCOUNTING command with FILE subcommand

    This section describes the ACCOUNTING command with the FILE subcommand.

    Usage

    Use the FILE subcommand to format unreduced DB2® data and store it in sequential data sets suitable for use by the DB2 load utility.

    Usage notes

    • In the case of CP parallelism, the logical Accounting record (aggregation of all the activity within the thread) is stored in the data set.
    • The records can be placed in DB2 tables, and you can produce reports by using a reporting facility such as Query Management Facility (QMF™).
    • You can also use the FILE data sets to generate CSV (comma-separated value) input-data. This CSV data can then be transferred to workstations and imported into spreadsheets to improve DB2 performance analysis using graphical representations or pivot tables. For more information refer to Reporting User's Guide (http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.xe.pe_db2.doc_5.1.1/ko2ru/ko2ru_about.htm).
    STATISTICS command with SAVE subcommand

    This section describes the STATISTICS command with the SAVE subcommand.

    Usage
    Use the SAVE subcommand to produce a VSAM data set containing interval records. After the data has been saved, you can:

    • Convert the save files to sequential data sets by using the save-file utility and load them into DB2® for subsequent use.
    • Restore and combine it with newly reduced data to produce long-term reports.
    • Restore it and use it in later reporting.

    You can also use the converted SAVE data sets to generate CSV (comma-separated value) input-data. This CSV data can then be transferred to workstations and imported into spreadsheets to improve DB2 performance analysis using graphical representations or pivot tables. For more information refer to Reporting User's Guide (http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.xe.pe_db2.doc_5.1.1/ko2ru/ko2ru_about.htm).


    STATISTICS command with FILE subcommand

    This section describes the STATISTICS command with the FILE subcommand.

    Usage

    Use the FILE subcommand to format unreduced DB2® data and store it in sequential data sets suitable for use by the DB2 load utility. The records can be placed in DB2 tables, and you can produce reports by using a reporting facility such as Query Management Facility (QMF™).

    You can also use the FILE data sets to generate CSV (comma-separated value) input-data. This CSV data can then be transferred to workstations and imported into spreadsheets to improve DB2 performance analysis using graphical representations or pivot tables. For more information refer to Reporting User's Guide (http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.xe.pe_db2.doc_5.1.1/ko2ru/ko2ru_about.htm).

    Usage notes

    • The data is stored in delta records in a sequential data set.

    Syntax of the FILE subcommand
    Read syntax diagram Skip visual syntax diagram
    >>-FILE--+---------------------------------+-------------------><
        '-+-| FROM/TO block |-----------+-'   
        | .-NOEXCEPTION-. |    
        +-+-EXCEPTION---+-------------+    
        | .-STFILDD1-. |    
        +-DDNAME--(--+- ddname---+--)--+    
        +-SPREADSHEETDD--(-- ddname--)-+    
        +-| INCLUDE/EXCLUDE block |---+    
        '-DSETSTAT--------------------'    


    Subcommand options

    The syntax diagram shows the options that are available with this subcommand. See OMEGAMON XE for DB2 PE subcommand options for comprehensive descriptions of these options. The following list gives additional or specific descriptions of selected options, where appropriate.

    FROM/TO
    Limits the range of delta records included in the data set by date and time.

    For details, see FROM/TO subcommand options.

    If you are reducing data, the times specified in REDUCE affect the data available for filing.

    EXCEPTION
    NOEXCEPTION
    Specifies EXCEPTION to include only those file entries containing fields with values outside user-specified limits. Otherwise, all records are included.

    If you use this subcommand option, your JCL must contain a valid DD definition for the ddname EXCPTDD. For more information about required ddnames, see EXCPTDD statement.

    DDNAME
    Specifies the ddname where the file data set is written. The default ddname is STFILDD1.
    SPREADSHEETDD
    Creates a data set in comma separated value (CSV) format. This data can be downloaded to a workstation and imported into a spreadsheet. The data set should be allocated using the following attributes:
    RECFM:
    VB
    LRECL:
    1 400 or greater

    The SPREADSHEETDD subcommand option reduces the STATISTICS FILE data to only virtual storage data (most notably IFCID 225).

    To prevent DB2 Performance Expert and DB2 Performance Monitor from writing FILE data to STFILDD1, specify DD DUMMY.

    The SPREADSHEETDD subcommand option cannot be selected as a predefined option within the Interactive Reporting Facility (IRF) and is also not available in the PWH Client user interface.

    Instead of this subcommand, you can use the Spreadsheet Input Data Generator utility to create CSV (comma-separated value) data for spreadsheet programs as described in Reporting User's Guide (http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.xe.pe_db2.doc_5.1.1/ko2ru/ko2ru_about.htm).

    INCLUDE/EXCLUDE
    Includes or excludes data associated with specific OMEGAMON® XE for DB2 PE identifiers.

    For details, see INCLUDE and EXCLUDE subcommand options, which lists other identifiers allowed with this command and subcommand combination, and OMEGAMON XE for DB2 PE identifiers.

    DSETSTAT
    Includes buffer pool data set statistics.

    Update 8: Changes to the 'ACCOUNTING command with REPORT subcommand' topic in Chapter 7 for PM73547 (January 2013)


    Subcommand options

    The syntax diagram shows the options that are available with this subcommand. See OMEGAMON XE for DB2 PE subcommand options for comprehensive descriptions of these options. The following list gives additional or specific descriptions of selected options, where appropriate.

    FROM/TO
    Limits the range of records included in the reporting process by date and time.

    For details, see FROM/TO subcommand options.

    You need to specify a REDUCE INTERVAL() for the FROM/TO subcommand under ACCOUNTING REPORT. Otherwise, you will see the following message:

    NO DATA TO REPORT - NO ADEQUATE INPUT DATA OR TOO RESTRICTIVE FILTERS.

    The reason for this message is that all accounting input data will be reduced by default to only one reporting interval. If you request several ACCOUNTING REPORTs with different FROM/TO subcommands, the INTERVAL() value that you chose should be the smallest of all FROM/TO intervals specified, as in the following example:

    ACCOUNTING
    REDUCE INTERVAL(15)
    REPORT DDNAME(ACCLONG1) /*ACCOUNTING REPORT*/
    FROM(,10:00:00)
    TO(,10:59:59)
    ...
    REPORT DDNAME(ACCLONG2) /*ACCOUNTING REPORT*/
    FROM(,11:00:00)
    TO(,11:29:59)
    ...
    REPORT DDNAME(ACCLONG3) /*ACCOUNTING REPORT*/
    FROM(,13:00:00)
    TO(,13:14:59)

    In order to ensure that no extra reporting interval is taken into account, specify either FROM or TO in a way that it does not overlap an adjacent interval boundary. In the following example, the report will show only one reporting interval every day FROM(,13:00:00) TO(,13:14:59):

    ACCOUNTING
    REDUCE INTERVAL(15)
    REPORT DDNAME(ACCLONG3) /*ACCOUNTING REPORT*/
    FROM(,13:00:00)
    TO(,13:14:59)

    As a comparison, the following report will report two adjacent reporting intervals every day - one from 13:00 to 13:15 and one from 13:15 to 13:30:

    ACCOUNTING
    REDUCE INTERVAL(15)
    REPORT DDNAME(ACCLONG3) /*ACCOUNTING REPORT*/
    FROM(,13:00)
    TO(,13:15)

    For more details, see BOUNDARY subcommand option and INTERVAL subcommand option.


Publication number

SH12-6922-00

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 #:

7022068

Modified date:

2013-01-10

Translate my page

Machine Translation

Content navigation