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

SQL_ATTR_DESCRIBE_OUTPUT_LEVEL WHEN SET AS 3 , THE SQLGETCONNECTATTR STILL
SHOWS AS 0

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Steps to reproduce 
 
opt callerror on 
opt echo on 
writeini common DescribeOutputLevel 3 
quickc 1 1 TEST123 
sqlsetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 2 
sqlgetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 
sqlsetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 3 
sqlgetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 
killenv 1 
 
 
Output 
 
> sqlsetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 2 
SQLSetConnectAttr: rc = 0 (SQL_SUCCESS) 
> sqlgetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 
SQLGetConnectAttr: rc = 0 (SQL_SUCCESS) 
Option (Unknown) = 2 
Output length = 4 
> 
> sqlsetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 3 
SQLSetConnectAttr: rc = 0 (SQL_SUCCESS) 
> sqlgetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 
SQLGetConnectAttr: rc = 0 (SQL_SUCCESS) 
Option (Unknown) = 0 
Output length = 4 
> 
 
Ideally when 3 is given the sqlgetconnectattr should be giving 3 
and not 0.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* When application program uses CLI.                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQL_ATTR_DESCRIBE_OUTPUT_LEVEL WHEN SET AS 3 using           * 
* SQLSetConnectAttr, THE SQLGetConnectAttr  STILL SHOWS IT AS  * 
* 0.                                                           * 
*                                                              * 
* > sqlsetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL 3      * 
*                                                              * 
* SQLSetConnectAttr: rc = 0 (SQL_SUCCESS)                      * 
*                                                              * 
* > sqlgetconnectattr 1  SQL_ATTR_DESCRIBE_OUTPUT_LEVEL        * 
*                                                              * 
* SQLGetConnectAttr: rc = 0 (SQL_SUCCESS)                      * 
*                                                              * 
* Option (Unknown) = 0                                         * 
*                                                              * 
* Output length = 4                                            * 
*                                                              * 
* >                                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to db2_v97fp5 or later releases.                     * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
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

Solution
db2_v97fp5 fixes the issue and after fix SQLGetConnectAttr will 
show the correct value.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.07.2011
12.12.2011
12.12.2011
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList