Assuming that you are using Windows XP, on Configuraiton Panel select "Admin tool" Icon and then "ODBC Data source"
Then, on the "System data source" tab press the "Add" button.
A new Window would pop up to give you the existing ODBC driver list on your PC.
Assuming that you are using Client Access, Select "Client Access ODBC Driver (32 bit) .
Another Window would pop up.
On the first tab:
- Select your AS/400 in the "System" drop down list.
- Give a name to your DSN in the "Data source name" field
- If you want to specify connection option (User profile, Signon dialog prompting) press the "Connection Option button to specify information.
On the second tab:
- Specify the SQL default library. This library will be your targetted library (for example if you create table in your SQL instruction without specifying a library)
- In the library list field, specify all libraries that you want to access seperated by a space.
On the 3rd tab:
- Specify the package library (This library will eventually contain your SQL package basic objects to communicate between yous AS/400 and your PC) .QGPL (default value) is fair enough.
For all other tab, you chould leave it as it is with default values.
There you go !
Have fun !
__________________
Taz
Last Wiki Answer Submitted: July 17, 2008 2:17 pm by DanTheMan 2395 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
Is there any need to install odbc driver in i5/OS machine.
That depends on what remote database you want to connect to. Most nowadays make Type 4 JDBC drivers available that get around the need for ODBC drivers. (A Type 4 driver is written in Java itself, so it only relies upon a compliant JVM.)
But various capabilities still indeed require a “driver”, although they generally wouldn’t be “ODBC” since that’s technically a Microsoft implementation of an Open DRDA subset. Such drivers must be obtained from the vendor of the remote database, and generally they are pretty pricey. For some cases, 3rd-party suppliers may have less costly solutions; e.g., their replacement “driver” lets your RPG think it’s talking to a remote database even though the 3rd-party driver is converting the conversation to and from an internal Type 4 JDBC driver or some other redirection.
Jacky,
These answers and tips from Search400.com might be helpful with this problem.
Accessing AS/400 data using Excel ODBC drivers
Redirect ODBC to a separate subsystem
Secure implementation of ODBC on the iSeries
i5/OS and Microsoft Office Integration Handbook, Third Edition — Chapter 3
Is there any need to install odbc driver in i5/OS machine.
Hi Jacky !
Nop ! no need’s to install anything on the 400.
The only thing you have to do is to make sure QSERVER and QSYSWRK sub-system have to be active. !
_________________
Taz
Is there any need to install odbc driver in i5/OS machine.
That depends on what remote database you want to connect to. Most nowadays make Type 4 JDBC drivers available that get around the need for ODBC drivers. (A Type 4 driver is written in Java itself, so it only relies upon a compliant JVM.)
But various capabilities still indeed require a “driver”, although they generally wouldn’t be “ODBC” since that’s technically a Microsoft implementation of an Open DRDA subset. Such drivers must be obtained from the vendor of the remote database, and generally they are pretty pricey. For some cases, 3rd-party suppliers may have less costly solutions; e.g., their replacement “driver” lets your RPG think it’s talking to a remote database even though the 3rd-party driver is converting the conversation to and from an internal Type 4 JDBC driver or some other redirection.
Tom