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

VISUAL STUDIO ENTITY DATA MODEL WIZARD MIGHT NOT SHOW ISERIES TYPE L AND
TYPE P TABLES

product:
DB2 COMMON CLIE / DBCMNCLNT / A10 - DB2
Problem description:
With Visual Studio 2012 the Entity Data Model Wizard might show 
only those table objects on an iSeries database server 
of Type T (SQL tables) and not those of Type L (Logical files) 
or Type P (Physical files).
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users having only VS2012 or VS2013 in their environment. * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* With Visual Studio 2012 the Entity Data Model Wizard might   * 
* show only those table objects on an iSeries database server  * 
* of Type T (SQL tables) and not those of Type L (Logical      * 
* files) or Type P (Physical files).                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2_v101fp4 or higher version.             * 
****************************************************************
Local Fix:
A possible workaround is to do the following sequence of 
actions: 
1) Uninstall DB2 and the Visual Studio Add-Ins 
2) Uninstall Visual Studio 2012 
3) Install Visual Studio 2010 
4) Install Visual Studio 2012 
5) Install DB2 and the Visual Studio Add-Ins
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
DB2_V101FP4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.12.2013
12.03.2014
12.03.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList