DB2 FOR LUW / DB2FORLUW / 950 - DB2

For a query executed multiple times via db2batch , the elapsed 
time for 2nd run and so on, does not reflect proper total 
elapsed time 
for the query. 
 
For example: 
 
Input file for db2batch contains the following queries: 
 
Query1: select * from t1 where r1=1 
Query2: select * from t1 where r1=1 
Query3: select * from t1 where r1=1 
...............

**************************************************************** 
* USERS AFFECTED:                                              * 
* All Users using db2batch to monitor multiple instances of    * 
* the same statement                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* You could use dynamic sql snapshot to get the execution      * 
* execution time and divide that by the # of executions to get * 
* an                                                           * 
* average execution time per execution.                        * 
****************************************************************

You could use dynamic sql snapshot to get the execution 
execution time and divide that by the # of executions to get an 
average execution time per execution.

Problem fixed in V95 Fixpack 10 and above.

You could use dynamic sql snapshot to get the execution 
execution time and divide that by the # of executions to get an 
average execution time per execution.

Vorgänger  : APAR is sysrouted TO one or more of the following: IC83894 IC87882 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

23.05.2012
28.08.2012
28.08.2012

9.5.FP10