DB2 CONNECT / DB2CONNCT / A10 - DB2

In the testing, it see that QueryTimeout is 2 & 
InterruptProcessingMode is 2. 
It is the timing of the sequence of events that can cause this 
issue. 
 
When the workload is running, CLI has sent the SQL request to 
DRDA. Even before the request has reached the server, the member 
has been stopped. 
Parallelly, the querytimeout has happened & with interrupt mode 
set to 2, the SQLCancel request is triggered. Here some changes 
were done in Galileo FP1 to set a interrupt flag. Now since no 
request has been sent to the server yet, the interrupt request 
gets the message "NO pending request need to be interrupted" 
If the interrupt flag is set to TRUE internally, the behaviour 
will be treated as non-seamless in CLI & SQL30108N will be sent 
to the application.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using sysplex setup. The interrupt processing mode     * 
* should be 2 & query time out should be set.                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V102 FP1 or later releases                        * 
****************************************************************

Set  InterruptProcessingMode as 0

DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

V101 FP2 fixes the issue

keiner bekannt / siehe Local-Fix

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

26.10.2012
17.12.2012
17.12.2012