Accounting Report and Trace Blocks
Accounting reports and traces are arranged in blocks. Each block contains accounting information about a particular activity. The layout of each block is presented followed by the field descriptions.
The layout of the Accounting report blocks and the corresponding trace blocks is similar, the main difference is that Accounting reports show times and events averaged over the number of threads, and accounting traces show times and events as totals for each thread.
- Have two decimal places behind the point
- Are whole numbers
- Have six decimal places behind the point
This topic shows each block in alphabetical order. Each field in the block is listed in the order that it appears, showing the field name (as shown in the long report and trace) followed by a description.
Each block is presented in the default layout. Some blocks can have columns, rows or fields that are not included in the default layout. For example, the SQL DCL, SQL DML, RID List, buffer pool and group buffer pool activity blocks have a /COMMIT column that is not shown in the default layout. You can include columns, rows, and fields not shown in the default layouts with user-tailored reporting (UTR).
Field names used in short reports and traces can vary slightly from those used in the long versions. This is to allow the layout of the printed report or trace to align properly.
- Not applicable is shown if DB2 never produces a counter value
in a specific context. Examples are:
- A counter is not available in one DB2 version.
- Counters are mutually exclusive.
- Not calculated is shown for a derived field where the value cannot
be calculated or is useless. Examples are:
- A divide by zero (percentages, ratios).
- Suppression of negative elapsed time values.
- Required counter values for calculation marked as
- Insufficient data or small counter values to allow significant statements (meaningless or misleading averages).
- Not present is shown for a field where DB2 can present values,
but does not in this instance. Examples are:
- When counter values are not generated because of operational conditions (a trace class is not active).
- An application does not provide a value because it is optional.
Short, Unique, or Long Names or Strings
- Short name or string
- A short name or short string is either the value of an original DB2® field if it less than or equal to the defined length of the field, or it is the abbreviation of a longer value which is populated in a field of varying length.
- Unique name or string
- A unique name or unique string is a generated string based on
the short string and its length, with a right-adjusted #-sign and
a sequence number. This sequence number depends on the amount of long
fields found during processing, which have the same string prefix
and length as the short string. For example:
- Long name or string
- A long name or long string is the complete string populated in a field of varying length. This depends on the context where it is used.