Why are the AA_CNT & AA_TIME fields on the DT Package/DBRM SQL Display zeros, when my COBOL program contains Static SQL, is bound with QUERYACCELERATION(ENABLE) & is executing in the IDAA box?
search cancel

Why are the AA_CNT & AA_TIME fields on the DT Package/DBRM SQL Display zeros, when my COBOL program contains Static SQL, is bound with QUERYACCELERATION(ENABLE) & is executing in the IDAA box?

book

Article ID: 15695

calendar_today

Updated On:

Products

Bind Analyzer for DB2 for z/OS SQL-Ease for DB2 for z/OS SYSVIEW Performance Management Option for DB2 for z/OS Plan Analyzer for DB2 for z/OS Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

This document explains why the AA_CNT & AA_TIME fields on the DT Package/DBRM SQL Display may be zeros, even though a COBOL program contains Static SQL, is bound with QUERYACCELERATION(ENABLE) & is executing in the IDAA box.



Why are the AA_CNT & AA_TIME fields on the DT Package/DBRM SQL Display zeros, when my COBOL program contains Static SQL, is bound with QUERYACCELERATION(ENABLE) & is executing in the IDAA box? 

Environment

z/OS 1.11 and above.

Resolution

Detector calculates stats at the end of an SQL request - so that only after it ends will values show up for a particular statement. Also at the end of the statement, those values are rolled up to the Plan and Program/Package level. This is true for all statements, not just those that run on the IDAA box.