DB2 FOR LUW / DB2FORLUW / 970 - DB2

When using CLP commands even with AUTOCOMMIT OFF combined with 
batch execution, the batch run will introduce an internal commit 
which might result in unexpected behaviour as anything that was 
executed previous to the batch will commit implicitly regardless 
of the setting of autocommit. 
 
Simple test case: 
 
db2 connect to sample 
 
cat  t_maria 
create table AAAAABBBBB(c1 int); 
 
 
1. db2 +c "create table AAAAAA(c1 int)" 
2. db2 +c -stf t_maria 
3. db2 rollback 
 
NONE of the tables should exist on the system after the 
rollback, but the execution with the batch file is doing a 
commit implicitly, so the first table creation gets committed. 
 
db2 list tables for all | grep -i AA 
AAAAAA                          MARIAJ          T 
2013-08-15-12.11.07.819349

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description. This problem was introduced in DB2    * 
* version 9.5 and Fix Pack 8, DB2 version 9.7 and Fix Pack 5   * 
* and DB2 version 10.1                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to  DB2 Version 9.7 and Fix Pack 9.                  * 
****************************************************************

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 was first fixed in DB2 Version 9.7 and Fix Pack 9.

not known / see Local fix

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

25.09.2013
16.12.2013
16.12.2013

9.0.,
9.7.