DB2 FOR LUW / DB2FORLUW / 950 - DB2

A boolean type of database or database manager configuration 
parameter should accept all the values of [YES,NO,ON,OFF]. 
However, the following parameters can ONLY accept either YES/NO 
or ON/OFF values: 
db cfg parameters: 
AUTO_DB_BACKUP,  AUTO_MAINT, 
AUTO_PROF_UPD,  AUTO_REORG, AUTO_RUNSTATS, AUTO_STATS_PROF, 
AUTO_TBL_MAINT, AUTORESTART, BLK_LOG_DSK_FUL, 
 DL_UPPER, INDEXSORT, SEQDETECT. 
 
dbm cfg parameters: 
CATALOG_NOAUTH, DATALINKS, DIR_CACHE, FEDERATED, INITDARI_JVM, 
INITFENCED_JVM, 
KEEPDARI, KEEPFENCED , DFT_MON_BUFPOOL, DFT_MON_LOCK, 
DFT_MON_SORT, DFT_MON_STMT, 
DFT_MON_TABLE, DFT_MON_TIMESTAMP , DFT_MON_UOW. 
 
The fix of this APAR will allow these parameters to accept all 
values of 
YES,NO,ON,OFF. 
 
This APAR also fixes the output values of the database 
configuration parameter TRACKMOD from the command "get db cfg". 
The current output values are 
"ON/OFF", which will be changed to "YES/NO" so they are 
consistent with the range list [Yes,No] documented in the 
information center.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 systems on all Linux, Unix and Windows platforms at  * 
* service levels from Version 9.5 GA through to Version 9.5    * 
* Fix Pack 8.                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 Fix Pack 9 or newer               * 
****************************************************************

DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in Version 9.5 Fix Pack 9

not known / see Local fix

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

13.05.2011
04.04.2012
04.04.2012

9.5.FP9