DB2 FOR LUW / DB2FORLUW / 970 - DB2

Two problems: 
1) DiagLevel=0 in db2cli.ini doesn't have any effect. The 
"DiagLevel=0" in db2cli.ini won't be picked up by client 
process,  and the diaglevel still stays at its previous value. 
 
2) After fixing problem 1), then, DiagLevel=0 in db2cli.ini will 
take effect in client process. Note that when diaglevel is 0, 
'Event' messages and admin messages  were still captured in 
db2diag.log. However, on DB2 client side, there is no need to 
log 'Event' messages when diaglevel is set to 0. Therefore, on 
client side, when diaglevel is set to 0, we will no longer 
capture 'Event' messages on db2diag.log 
 
Note that after the fix, to totally shut down db2diag.log 
logging on db2 client side, 
beside setting "DiagLevel=0" on db2cli.ini, one needs to set 
"NotifyLevel=0" in db2cli.ini too.

**************************************************************** 
* 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
 

Problem first fixed in Version 9.7 Fix pack 6.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC84496 IC84511 
Nachfolger : 

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

17.02.2012
22.06.2012
22.06.2012

9.7.FP6