ACCOUNTING command with TRACE subcommand

Usage

Usage notes

• An entry in an Accounting trace is referred to as a logical Accounting record as it can consist of several physical Accounting records (IFCIDs 3 and 239).
• Up to five traces can be requested in a job step.

Syntax of the TRACE subcommand

Subcommand options

The syntax diagram shows the options that are available with this subcommand. See 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 trace by date and time.

For details, see FROM/TO subcommand options.

LAYOUT

Specifies the name of a report layout. You can specify one of the supplied layouts or one that you have previously tailored:

SHORT

This is the default.

LONG

This option provides detailed thread-related data. You can also use other functions such as Record Trace and SQL Activity to find detailed Db2 trace data.

Historical Reporter migration layouts

Use the Historical Reporter migration layouts to help you identify OMEGAMON for Db2 PE data that was previously shown in the reports of the OMEGAMON® Historical Reporter. The migration layouts include:

• Options for OMEGAMON Historical Reporter Accounting reports
• Options for OMEGAMON Historical Reporter Statistics reports

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.

For information about tailoring report layouts, see the Reporting User's Guide.

EXCEPTION

NOEXCEPTION

Specify EXCEPTION if you want to show those accounting trace entries with at least one field in exception status. Otherwise, a standard report is produced.

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

TOP

Identifies trace entries with a high value in certain fields, you can produce an Accounting trace with TOP lists. TOP lists indicate which entries on the trace have the highest value in the field you have specified by using the TOP subcommand option.

For more information about TOP processing, see TOP subcommand option and Examples of TOP processing, as well as the Reporting User's Guide. You can specify:

number

By default, the TOP list contains the top ten entries, but you can change the number to anything from one to fifty.

ONLY

ONLY allows to use TOP as a filter. When TOP is requested as a filter, the index is not shown. For example, the trace produced by the command following ONLY shows the top 3 entries for the default TOP field, elapsed time in application (INAPPLET). The keyword ONLY is valid wherever a resource name can be used.

ACCOUNTING
   TRACE
      TOP (3 ONLY)

*

Specifies any combination of the fields. You can generate reports showing TOP lists for all the fields available for use with the TOP subcommand option.

keyword

TOP lists for package fields report the maximum values of these fields in individual packages within a trace entry. TOP lists for buffer pool fields contain the totals for all the buffer pools.

The following list shows the keywords that these fields are specified by:

INAPPLET

The class 1 elapsed time (in an application). This value is an average.

If no TOP subcommand option is specified, the default is class 1 elapsed time (INAPPLET).

BUFUPDTS

The number of buffer updates. This value is an average.

CMPERUPD

The ratio of the sum of commits and rollbacks to the sum of SQL UPDATE, SQL INSERT, and SQL DELETE statements.

DCLSTAT

The total number of DCL statements executed.

DDLSTAT

The total number of DDL statements executed.

DMLSTAT

The total number of SQL DML statements executed.

GETPAGES

The number of Getpage requests. This value is an average.

INAPPLPT

The class 1 CPU time in an application. This value is an average.

INAPPLWT

The class 1 waiting time in an application. This value is an average.

INDB2ET

The class 2 elapsed time accumulated in Db2. This value is an average.

INDB2PT

The class 2 CPU time in Db2. This value is an average.

INDB2WT

The class 2 waiting time in Db2. This value is an average.

MAXWRKF

Identifies the threads with the highest values for the field MAX WFILE BLKS (Db2 field QWAC_WORKFILE_MAX) which is shown in the Highlights data blocks. This value is a maximum.

NOTACCT

The time not accounted in Db2. You use this time to determine whether there is a large percentage of time that has not been captured within the Db2 Accounting record. This value is an average.

OUTDB2ET

The elapsed time outside Db2. This value is an average.

OUTDB2PT

The CPU time outside Db2. This value is an average.

OUTDB2WT

The waiting time outside Db2. This value is an average.

PINDBET

The total elapsed time for executing the package or DBRM. This value is an average.

PINDBPT

The CPU time spent by the package or DBRM (class 7). This value is an average.

PNOTACCT

The total unaccounted time in Db2 caused by the execution of the package or DBRM. This value is an average.

PTSUSTME

The waiting time for the package or DBRM caused by a class 8 suspension. This value is an average.

SYNCREAD

The number of synchronous read I/O operations. This value is an average.

TOTPREF

The number of all types of prefetch requests. This value is an average.

TOTSUSP

The number of suspensions. This value is an average.

TOTSUSTM

The waiting time for all class 3 suspensions. This value is an average.

UPDPERCM

The sum of SQL UPDATE, SQL INSERT, and SQL DELETE statements executed.

DDNAME

Specifies the data set where the trace is written. The default ddname for the first trace is ACTRCDD1. The default ddnames for the second to fifth traces are ACTRCDD2 through ACTRCDD5.

INCLUDE/EXCLUDE

Includes or excludes data associated with specific OMEGAMON 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 for Db2 PE identifiers.

Some care is needed when using PLANNAME as a filter in a DDF environment, see Special considerations for DDF trace data.