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 IT07411 Status: Closed

ODBC APPLICATIONS RETURN NO ROW AFTER UPGRADING THE DB2 GATEWAY

product:
DB2 CONNECT / DB2CONNCT / A50 - DB2
Problem description:
If you have an ODBC application that connects to a DB2 server 
through a DB2 Gateway, your SELECT queries may return SQL0100W ( 
(SQL_NO_DATA_FOUND ) after upgrading your DB2 Gateway to DB2 
10.5 FP4 (or later), even if those queries are supposed to 
return data. 
 
Example : 
 
DB2 Client -> DB2 Gateway ( 10.5 FP4 or FP5 ) -> DB2 Server 
 
On the DB2 client : 
 
more test.clp  : 
opt autocommit on 
opt echo on 
opt callerror on 
sqlallocenv 1 
sqlallocconnect 1 1 
sqlsetconnectattrw 1 SQL_ATTR_COMMITONEOF SQL_COMMITONEOF_ON 
SQLDriverConnectW 1 0 "DSN=SAMPLE;uid=user;pwd=password;" -3 255 
SQL_DRIVER_NO_PROMPT 
sqlallocstmt 1 1 
sqlexecdirectw 1 "select 'RESULT' from sysibm.sysdummy1" sql_nts 
sqlfreestmt 1  SQL_CLOSE 
killenv 1 
 
db2cli < test.clp 
.... 
> sqlexecdirectw 1 "select 'RESULT' from sysibm.sysdummy1" 
sql_nts 
SQLExecDirect: rc = 100 (SQL_NO_DATA_FOUND) 
....
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ODBC users with DB2 z/OS server                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 FP7 or later                             * 
****************************************************************
Local Fix:
add the following parameter in your db2dsdriver.cfg file 
    <parameter name="CommitOnEOF" value="0"/>
Solution
The problem was first fixed in DB2 10.5 FP7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.03.2015
19.01.2016
19.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList