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

Compilation error due to sqlcli1.h having c++ style comments for attribute
SQL_ATTR_SQLCODEMAP

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
sqlcli1.h has c++ style comments used for attribute 
SQL_ATTR_SQLCODEMAP which can give compilation error for 
applications using 
compiler that does not support it. 
 
// SQL_ATTR_SQLCODEMAP values 
#define SQL_SQLCODEMAP_NOMAP          1 
#define SQL_SQLCODEMAP_MAP            2
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v101fp1 or later.                             * 
****************************************************************
Local Fix:
users can set -qlanglvl compiler option to stdc99 or extc99 
or 
specify -qcpluscmt
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
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

Solution
Fixed in db2_v101fp1. 
Compilation issue fixed.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.06.2012
02.11.2012
02.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList