DB2 Reporting on User Activity
DB2 user activity reporting does not generally require access to the most detailed level of data.
rm
By default, the
MICS
User/Plan Activity files (DB2DSU and DB2DSP) are inactivated in the DETAIL timespan. However, data summarization in higher levels of granularity must be accurate and must prevent data duplication, overlapping, or incomplete measurements.You can determine if any query is enabled for CP parallelism, at any point within the reporting interval, even if you do not have access to DB2 system information or parameters.
When the DETAIL timespan is active for the user activity files and you are reporting on a glandular level, use the Special Transaction Type Identifier (DB2PTASK) to identify each observation.
NONE
Indicates that the observation represents the activity of a sequential query.
ACUMAC
Indicates a record representing the DB2 ACCUMACC summarization of two or more DDF or RRSAF queries.
PARENT
Indicates that the observation represents only the activity of the originating task of a parallel query.
CHILD
Indicates that the observation represents the activity of a single parallel subtask (individual child records are generated when the DB2 system parameter PTASKROL is set to NO).
ROLLUP
Indicates that the observation represents the summarized activity of all parallel child subtasks. Summarized child roll-up records are generated when the DB2 system parameter PTASKROL is set to YES.
If you report on higher levels than DETAIL, then DB2PTASK is no longer meaningful. However, the database maintains an accumulated counter containing the number of parallel tasks that are created, DSUPCNT. If all the queries are sequential, DSUPCNT is equal to zero. On the other hand, if DSUPCNT is positive, at least one query in the reporting interval used CP parallelism.
The following guidelines are intended to assist you by using correct
MICS
data elements under various circumstances.- DB2 Queries Enabled for CP Parallelism
- DB2 Queries That Do Not Use CP Parallelism