home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC78852 Status: Closed

NO ERROR RETURNED TO A .NET APPLICATION AFTER A ROLLBACK OF A QUERY DUE TO
COMMANDTIMEOUT.

product:
DB2 CONNECT / DB2CONNCT / 950 - DB2
Problem description:
Even after a rollback of a query due to CommandTimeout of End 
Chain statement in .NET applications or End compound statement 
in CLI applications, no error is returned to the application. 
On Command Timeout, the CLI sends a SQLCancel() interrupt to the 
server. 
 
Irrespective of Interrupt  Enabled/Disabled at zOS server, upon 
Command Timeout CLI invokes SQlCancel() and rollbacks the 
transaction, but CLI rely on the server for interrupt error 
(-952). If no error is returned by the server, CLI also fails to 
return the error to the application.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V9.5 CLI/.NET applications.                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* No error message is returned to the application after        * 
* rollback of a query due to CommandTimeout of END CHAIN       * 
* statement in .NET applications or END COMPOUND statements in * 
* CLI applications.                                            * 
*                                                              * 
* On Command Timeout, the CLI sends a SQLCancel() interrupt to * 
* the server.                                                  * 
* Irrespective of INTERRUPT Enabled or Disabled at zOS server, * 
* upon Command Timeout CLI invokes SQlCancel() and rollbacks   * 
* the transaction, but CLI rely on the server for interrupt    * 
* error (-952). If no error is returned by the Z/OS server due * 
* to INTERRUPT disabled, CLI also fails to return the error to * 
* the application.                                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.5 FP9.                                     * 
****************************************************************
Local Fix:
Increase the 'CommandTimeout' valus in the connection String.
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 V9.5 FP9.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC79087 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.09.2011
27.04.2012
27.04.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList