Reverse Engineering with IBM DB2 Universal Database

[Dennis Vipond]

I am trying to Reverse Engineer a DB2 Mainframe DB but cannot get the IBM DB2 Universal Database driver to work.
I select the driver and my Data source and click Next.
The Connect Data Source pop up appears for my user name and password.
I enter my user name and password and click on OK.
The pop up disappears and I'm back on the Reverse Engineer Wizard form.

I have DB2 Connect on the machine version 7.2
Running Windows 2000 sp 4
Visio Enterprise Arch. - Came with Visual Studio .NET 2003

I can use the ODBC Generic Driver,
but I cannot reverse Triggers, Check Clauses, Views or Stored Procedures
I also get a Warning!
"You are using a Visio ODBC Generic Driver' driver to connect with a 'DB2' DBMS datasource. By using an incompatible driver, it is possible that the catalog information retrieved will be incomplete."

Is there a trick to using the IBM DB2 Universal Database driver?

 

[Al Edlund]

I'd suggest that since it's a M$ tool, it's lack of support for OEM internals should not be a surprise. The only surprise is that it works at even a basic level. Within the databases I have examined, I haven't seen any return internals such as stored procedure calls, triggers, etc.
I also get the occasional errors on DB2 (M$ has a real problem with cardinality attributes) but it does give me the tables that I ask for (basic SQL functionality)

DB2 Connect Personal 8.1
XP-PRO-Tablet Edition (xp-sp2-rc2)
Visio 2003

Al
I am trying to Reverse Engineer a DB2 Mainframe DB but cannot get the IBM DB2 Universal Database driver to work.
I select the driver and my Data source and click Next.
The Connect Data Source pop up appears for my user name and password.
I enter my user name and password and click on OK.
The pop up disappears and I'm back on the Reverse Engineer Wizard form.

I have DB2 Connect on the machine version 7.2
Running Windows 2000 sp 4
Visio Enterprise Arch. - Came with Visual Studio .NET 2003

I can use the ODBC Generic Driver,
but I cannot reverse Triggers, Check Clauses, Views or Stored Procedures
I also get a Warning!
"You are using a Visio ODBC Generic Driver' driver to connect with a 'DB2' DBMS datasource. By using an incompatible driver, it is possible that the catalog information retrieved will be incomplete."

Is there a trick to using the IBM DB2 Universal Database driver?

 

[mraasch]

I am having the same problem with our IBM iSeries computer (AS/400) which
is running on OS 5.2 and windows XP and visio 2000. I have created a log
and the driver that comes with visio is trying to get information from the
system catalog with invalid library and file information (ie.
syscat.functions). That library and table do not exist on our computer.
They(being microsoft) obviousely did not test this functionality.