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

TYPEDEF IS NOT WORKING AS EXPECTED WHEN TWO OR MORE TYPEDEF STRUCTURES WITH
SIMILAR MEMBER NAME EXIST.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
In an SQC file, if we have two or more typedef struct 
declarations with similar member name in it, DB2 precompiler 
might throw "SQL0008N  The token <token> found in a host 
variable declaration is not valid." error, due to the issue with 
how the host variables table is stored.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 FixPack 3                            * 
****************************************************************
Local Fix:
Not available.
available fix packs:
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
Problem was first fixed in DB2 UDB Version 10.1 FixPack 3
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC94948 IC95477 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.06.2013
27.09.2013
27.09.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList