3. REPORTS › 3.1 Tabular Reports Overview › 3.1.6 DB2 Plan Performance Summary Report › 3.1.6.1 PLAN Performance Summary Report Format
3.1.6.1 PLAN Performance Summary Report Format
The PLAN Performance Summary Report contains the following
sections:
o Identification
o PLAN Summary
o Report Page End
Identification Section
RUN DATE Date the report was created.
SYSID Logical system identifier.
DB2 SYSTEM DB2 subsystem identifier. (DB2ID)
RELEASE DB2 subsystem release level.
(DB2RELN)
REPORTING PERIOD Earliest and latest dates and
times found within the data.
PLAN Summary Section
PLAN DB2 PLANs included in this
report. (DB2PLAN)
FACILITY Facility identifier of requesting
environment (IMS, CICS, BATCH,
and so on) (DB2CONN)
COUNT Total number of PLAN executions
used to generate this report
line. This value is calculated
as the greater of the number of
threads initiated (or the number
of parent tasks when query CP
parallelism is in use) or sum of
the commit phase 2 + aborts,
i.e., DSPNTHRD or (DSPCOMM2 +
DSPABORT)
TOTAL TCB SEC Total TCB time for the users/
PLANs/facilities included in this
report. This time may include
non-DB2 application TCB time for
facilities other than CICS.
(DSPTCBTM)
AVG TCB SEC Average TCB seconds per PLAN
execution. (DSPTCBTM/COUNT)
AVG ELAPSED Average elapsed time per PLAN
execution. This number is
computed using the following
algorithm:
- If COUNT is equal to DSPNTHRD
and any of the PLAN executions
used query CP parallelism:
<AVG ELAPSED> = DSPELPTM/COUNT
- Otherwise:
<AVG ELAPSED> = DSPTELPT/COUNT
TOTAL GETPAGE Total GETPAGE requests for all
executions of this PLAN.
(DSPSGPGR)
AVG GETPAGE Average GETPAGE requests for each
PLAN execution.
(<TOTAL GETPAGE>/COUNT)
AVG SYNC. READ Average synchronous reads per
execution of this PLAN. This
count does not include the
asynchronous sequential prefetch
reads. Total synchronous reads
are calculated as follows:
TOTAL SYNC READ = DSPSRIO
Then the average is computed.
(<TOTAL SYNC READ>/COUNT)
AVG SEQ. PREFETCH Average Prefetch reads per
execution of this PLAN. First
the total prefetch reads are
calculated as follows:
TOTAL SEQ. PREF = DSPSPRFH
Then the average prefetch read
requests are calculated as
follows:
(<TOTAL SEQ. PREF>/COUNT)
AVG MAX PG LOCKS The average maximum page locks
per PLAN execution is derived by
first summing all maximum page
lock counts for this plan
(DSPMXPL); then dividing that SUM
by the PLAN execution count
(COUNT). The result shows the
maximum number of pages that are
locked for each PLAN on average.
(DSPMXPL/COUNT)
AVG UPDATE PAGE The average number of unit-of-
work pages updated per PLAN
execution. First the total unit-
of-work page updates are
calculated as follows:
Then the average is calculated.
(<TOTAL UPD PAGE>/COUNT)
TOTAL DEADLOCK Total deadlocks detected by DB2
for all executions of this PLAN.
(DSPDEAD) The amount of time
allowed before deadlock detection
is determined at DB2 startup from
the IRLM parameters.
(DSPTIMO)
TOTAL SUSPEND Total suspend requests for this
PLAN. (DSPSUSP)
TOTAL TIMEOUT Total timeouts detected by DB2
for all executions of this PLAN.
A timeout occurs for PLAN waiting
for resources that are
unavailable. The amount of time
allowed before timeout processing
is initiated, is determined at
DB2 startup from the IRLM
parameters. (DSPTIMO)
TOTAL ABORT Total PLAN aborts for all
executions of this PLAN.
(DSPABORT)
Report Page End
REPORTING PERIOD Earliest and latest dates and
times found within the data.