Package Identification - Trace

This topic shows detailed information about Accounting - Package Identification - Trace.

Accounting - Package Identification - Trace

The field labels shown in the following sample layout of Accounting - Package Identification - Trace are described in the following section. 


PCKNAME             VALUE
------------------  ------------------
TYPE                PACKAGE
LOCATION            DSNDA1B
COLLECTION ID       NULLID
PROGRAM NAME        SYSSN201
CONSISTENCY TOKEN   5359534C564C3032
ACTIVITY TYPE       nnlast_act_type
ACTIVITY NAME       nnlast_act_name
SCHEMA NAME         nnlast_schema
INCOMPATIBILITY     NO
SUCC AUTH CHECK     NO
NBR OF ALLOCATIONS                   1
SQL STMT - AVERAGE               30.00
SQL STMT - TOTAL                    30
NBR RLUP THREADS              nnnnnnnn
PCKNAME

This label is replaced by the package name, or, if ORDER (ACTNAME) was in effect, the package activity name. An activity name is truncated if it is longer than 8 characters.

Field Name: PCKNAME

TYPE

An indicator of whether the block describes a package or a DBRM. Possible values are PACKAGE, DBRM, and BOTH. BOTH can be shown in reports if there are packages and DBRMs with the same program name.

Field Name: ADPCKTYP

LOCATION

The location name.

If this field is blank in trace or report, the package or DBRM was executed locally. If it is not blank, all times represent the time spent locally to execute the remote package for this APPL_DIR requester.

This field is invalid (N/P) if summary rollup data is present.

Field Name: QPACLOCN

This is an exception field.

COLLECTION ID

The package collection ID. This field does not apply to DBRMs. If the program name cannot be identified, this field is not present in report or trace.

This field is invalid if summary rollup data is present. It can have the following value in:
  • Accounting trace and report: N/P
  • The Accounting FILE and SAVE PROGRAM table: blank

Field Name: QPACCOLN

This is an exception field.

PROGRAM NAME

The program name (package ID or DBRM name).

In the case of rollup data (Accounting data of DDF/RRSAF threads and parallel tasks accumulated by DB2), the following value is shown *ROLSUM*.

Field Name: QPACPKID

This is an exception field.

CONSISTENCY TOKEN

The program (package or DBRM) consistency token.

This field is invalid (0) if summary rollup data is present.

Field Name: QPACCONT

ACTIVITY TYPE
The type of activity. The following values indicate how the package was loaded:
ALL TYPES
In a data block that reports totals it is set to ALL TYPES.
STORED PROC
When running an external procedure
TRIGGER
When running a trigger
UDF
When running a user-defined function
NATIVE SQL PROC
When running a native SQL procedure
NATIVE UDF
When running a native UDF procedure (a non-inline user-defined function)
NONNESTED
Indicates that none of the above values is true
MULTIPLE
Indicates that packages with the same key but with different activity types were running
N/P
Invalidated in case of rollup summary
The nested activity values that are shown in column NEST_ACTIVITY_TYPE of the table DB2PMFACCT_PROGRAM are:
S
For Stored Procedure
T
For Trigger
U
For UDF
Q
For native SQL procedure
D
For Native UDF
N
For nonnested (other)
blank
For invalidated in case of rollup summary

This field is invalid if unique or summary rollup data is present.

Field Name: ADPATYP

ACTIVITY NAME

The name of the nested activity.

This field contains the name of the nested activity if the package is defined for a:
  • Trigger
  • Stored procedure
  • User-defined function (UDF)
  • Native SQL procedure
  • Non-inline UDF

In a data block that reports totals it is set to ALL NAMES.

This field is invalid if summary rollup data is present.

It can have the following value in:
  • Accounting Trace and Report: N/P
  • The Accounting FILE and SAVE PROGRAM tables: blank

Field Name: ADPAANM

SCHEMA NAME

Schema name of the nested activity.

If the package is defined for a trigger, stored procedure, or user-defined function, then this field contains the name of the schema to which the nested activity belongs. It can have the following value in:
  • Accounting Trace and Report: N/P
  • The Accounting FILE and SAVE PROGRAM tables: blank

This field is invalid if summary rollup data is present.

Field Name: ADPASCH

INCOMPATIBILITY

The package has an incompatible function. IFCID 0366 and 0376 have information about the incompatible function.

Field Name: QPACINCOMPAT

SUCC AUTH CHECK
For Accounting traces, this field indicates whether authorization information was found for this package without accessing the DB2 catalog. This field is valid for non-rollup data. Possible values are:
  • YES
  • NO
  • N/A if DB2 or later is used
  • N/P, this field is invalid for Accounting trace
  • blank, this field is invalid in the Accounting FILE PROGRAM table
Note: This field is invalid if unique or summary rollup data is present.

Field Name: ADPCKAUT

NBR OF ALLOCATIONS

This value can be one of the following:

  • In general, the number of times a package was invoked by a different package. For the first package run by an application, the initial call counts as a package switch. If this package called a nested package (such as a trigger, UDF, or stored procedure), a switch will not be counted upon return from such a package.
  • If REPORT ORDER (ACTNAME) is specified, the number of times a package of a special activity type is invoked from a different package depends on the following:
    • If IFCID 233 or 380 is available, the invocations of stored procedures (SP) are counted based on the available IFCID. If both IFCIDs are available, IFCID 380 is the preferred one for SP reporting. Subprograms called by these SPs are not taken into account.
    • If IFCID 233 or 381 is available, the invocation of user-defined functions (UDF) are counted based on the available IFCID. If both IFCIDs are available, IFCID 381 is the preferred one for UDF reporting. Subprograms called by these UDFs are not taken into account.
    • If neither IFCID 233, 380, nor 381 is collected, all invocations of an activity type are counted. The sum also includes the number of subprograms.

Field Name: APACSWIT

SQL STMT - AVG

The number of SQL statements issued in this package or DBRM.

This number may not be equal to the total number of SQL statements in the QXST data section because QXST does not count all SQL statements. For example, it does not count commit or rollback statements.

Note: This field is shown for the following field labels in Accounting trace:
  • SQL STMT - TOTAL
  • SQL STMT - AVERAGE:

Field Name: QPACSQLC

This is an exception field.

SQL STMT - TOTAL

The number of SQL statements issued in this package or DBRM.

This number may not be equal to the total number of SQL statements in the QXST data section because QXST does not count all SQL statements. For example, it does not count commit or rollback statements.

Note: This field is shown for the following field labels in Accounting trace:
  • SQL STMT - TOTAL
  • SQL STMT - AVERAGE:

Field Name: QPACSQLC

This is an exception field.

NBR RLUP THREADS

This value can be one of the following:

  • In general, the number of threads to roll data into this QPAC data section. Non-rollup QPACs have a value of 1 and rollup QPACs have a value of 1 or more. This number is used as a divisor for calculating averages for package class 7, 8, or 10 times and events.
  • If REPORT ORDER (ACTNAME) is specified, the number of threads to roll data into this QPAC data section of a special activity type depends on the following:
    • If IFCID 233 or 380 is available, the number of threads to roll data into this QPAC data section for stored procedures (SP) is counted based on the available IFCID. If both IFCIDs are available, IFCID 380 is the preferred one for SP reporting. Subprograms called by these SPs are not taken into account.
    • If IFCID 233 or 381 is available, the number of threads to roll data into this QPAC data section for user-defined functions (UDF) is counted based on the available IFCID. If both IFCIDs are available, IFCID 381 is the preferred one for UDF reporting. Subprograms called by these UDFs are not taken into account.
    • If neither IFCID 233, 380, nor 381, is collected, the total number of threads to roll data into this QPAC data section is counted. The sum also includes the number of subprograms.

Field Name: QPACRLNU