Hi Peeps,
Being a simple RCAD guy, I don't usually get mixed up in this sort of thing, but hopefully I can help out Kbrimley and Dataprincess.. have you tried the following:>?
Requirements for connecting to the IBM DB2 database through ODBC:
======================================================================
0) Make sure that an IBM DB2 server is already setup and running on the backend AS/400 machine.
1) Acquire and install the IBM DB2 Client Software (obtained from IBM).
2) Once the IBM DB2 client has been properly installed and configured on the machine, then a connection via ODBC to DB2 requires that either:
a) Connectivity 5 (formerly known as DDCS - Distributed Database Connectivity Service). This software has to be purchased separately from IBM. CR does not ship this product.
OR
b) Install the ODBC driver which shipped with the IBM DB2 database. If this ODBC driver is used to connect, then Connect 5 does not need to be purchased.
3) The Connectivity 5 (or DDCS - Distributed Database Connectivity Software/Service) add-on piece is required in order to use our CRDB2xx.DLL ODBC driver or NATIVE DB2 driver called P2SDB2.DLL that Crystal Decisions ships with.
Method of access in the Report Designer via our ODBC driver and via our native DB2 driver:
method#1: Report Designer---->P2SODBC.DLL----->ODBC32.DLL---->ODBC DRIVER---->DDCS---->DB2 Client----->DB2 Server
method#2: Report Designer---->P2SDB2.DLL----->DDCS---->DB2 Client----->DB2 Server
(4) Install CR or SI (which also comes with a Report Designer component). They both ship with an Intersolv ODBC driver for IBM DB2 called CRDB2xx.DLL. In addtion, they will install a native DB2 driver called P2SDB2.DLL.
NOTE#1: There is a DB2 Native Connection Utility (that comes with the DB2 Universal Server product) called: "Client Configuration Assistant". To use this to test connectivity, do the following:
- Highlight Database.
- Click Test button.
- Enter UserID and Password.
- Either a successful or failed connection will occur. This will verify whether the IBM DB2 client has been properly installed and configured.
NOTE#2: When one sets up an ODBC datasource using our CRDB2xx.DLL, all that is required is the Datasource name and Database Name.
NOTE#3: Scenario: using CR or SI to connect with DB2 on an AS/400. A successful connection is made via ODBC but cannot be made via the DB2 native driver that ships with our products.
This does work on an NT and RS6000 platform but not on an AS/400. It is likely that the cause is the lack of the right messenger on AS/400 (DDCS vs DRDA). Apparently, IBM only ships the right one on AS/400 as an add-on that you buy and pay for per user. This is fine on an NT/RS6000 platform but it is an add-on for AS/400.
NOTE#4: A user does not have support for stored procedures unless the user uses crystal's native DB2 driver and this is working with Connect 5 with DB/2 on an AS/400.
Cheers,
-Bruce Seagate Certified RCAD Specialist.
-Bruce Thuel-Chassaigne
roadkill150@hotmail.com