INDB2_CPU is higher than INDB2_TIME on the Detector Exception screens.

Products

• Detector for DB2 for z/OS

Issue/Introduction

Sometimes INDB2_CPU is higher than the INDB2_TIME on the Detector for Db2 for z/OS (PDT) Exception screens.
How is that possible?

Resolution

It is possible for the INDB2_CPU to be higher than INDB2_TIME for the following reasons:

INDB2_TIME:
The total or average amount of elapsed time spent executing within DB2 for the thread, unit of work, plan, program, SQL activity, SQL call(s),
application, or user.

INDB2_CPU:
The total or average amount of CPU time spent executing within DB2 for the thread, unit of work, plan, program, SQL activity, SQL call(s), application,
or user.  This value includes both standard CPU and zIIP CPU times.

It may be larger than the corresponding INDB2_TIME because the zIIP CPU time component is normalized to be equal to what the time on a standard CPU would
have been. For SQL requests that use CPU parallelism the INDB2_CPU is accumulated across all of the parallel tasks.

The above explanation can also be found on the online help panels for INDB2_TIME and INDB2_CPU.