DB2 CONNECT / DB2CONNCT / 970 - DB2

If you have a CLI application that calls SQLGetDiagField(), the 
error message returned may be incomplete because CLI calls 
SYSIBM.SQLCAMESSAGE() with incorrect parameters. 
 
Example : 
If your CLI application is calling the following procedure CALL 
SYSPROC.ADMIN_INFO_SYSLOG 
(NULL,'*','2012-05-06','00.01.00','2012-05-30','23.00.00',3000,? 
) and it fails with error -471 : 
 
the message returned is 
 
SQLGetDiagField( pDiagInfo="[IBM][CLI Driver][DB2] INVOCATION OF 
FUNCTION OR PROCEDURE SYSPROC.ADMIN_INFO_SYSLOG", pcbDiagInfo=84 
) 
    <--- SQL_SUCCESS   Time elapsed - +1.237700E-002 seconds 
 
instead of 
 
SQLGetDiagField( pDiagInfo="[IBM][CLI Driver][DB2] INVOCATION OF 
FUNCTION OR PROCEDURE SYSPROC.ADMIN_INFO_SYSLOG FAILED DUE TO 
REASON 00E79106", pcbDiagInfo=114 ) 
    <--- SQL_SUCCESS   Time elapsed - +1.237700E-002 seconds

**************************************************************** 
* USERS AFFECTED:                                              * 
* db2connect users using cli.                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v97fp7 or later releases.                     * 
****************************************************************

n/a

DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 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
 

db2_v97fp7 contains fix of this issue. After the fix, user will 
get correct error message.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC85658 
follow-up : 

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

22.06.2012
24.10.2012
24.10.2012