DB2 FOR LUW / DB2FORLUW / 970 - DB2

If a page corruption is first detected by a DB2 prefetcher we 
should create the FODC directory and call the 
db2cos_datacorruption call out script. 
 
Currently only the call out script is being called by the 
prefetcher edu, but no FODC package is setup so that all data is 
dumped just under DIAGPATH directory. Only when DB2 attempts to 
re-read the bad page via a different code path via an db2agent 
edu, 
then we create the FODC directory under 
<DIAGPATH>/FODC_BadPage_<date>. 
This behavior is inconsistent and need to be changed. We should 
create the directory in all cases.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 6.                       * 
****************************************************************

DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in Version 9.7 Fix Pack 6.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC84313 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

20.09.2011
19.06.2012
19.06.2012

9.7.FP6