We are currently using the JDBC driver (COM.ibm.db2.jdbc.app.DB2Driver) that comes with DB2 Connect to retrieve data from our iSeries. We discovered that in order to use this driver, we have to specify in the SQL statement the library that the file(s) are located in. We would like the library list to be used to find the file(s). We know that the JDBC driver that comes with the iSeries Toolkit for Java (com.ibm.as400.access.AS400JDBCDriver)...
can use the library list and we have it working in another application.
A third party provider was telling us we needed DB2 Connect for this particular application. My question: Is there any significant difference between these two JDBC drivers? I guess the driver that comes with DB2 Connect is called a "Type 2" driver, but I'm not sure if that is significant or not.
The Type 2 driver vs. the iSeries type 4 JDBC driver should not matter. There are probably some minor differences between the JDBC driver like the library list support issue that you have already discovered. However, I'm not aware of any differences that would prevent a third-party application from using the Toolbox JDBC driver. I would ask the third-party provider to tell you why they cannot the Toolbox JDBC driver -- my guess is that they have not taken the time to test with the Toolbox JDBC driver. There were some rare cases in the past where DB2 Connect had to be used instead of the iSeries middleware, but those deficiencies were eliminated.
MORE INFORMATION ON THIS TOPIC
Search400.com's targeted search engine: Get relevant information on DB2/400.
The Best Web Links: tips, tutorials and more.
Check out this online event, Getting the Most out of SQL & DB2 UDB for the iSeries.
Dig deeper on Oracle on iSeries
Related Q&A from Kent Milligan
To monitor members stuck within a physical file on AS/400, you can periodically use the display file description (DSPFD) command to create an output ...continue reading
Create a host variable of the where in statement on the fly with dynamic SQL.continue reading
To solve the SQL error -321 on IBM i6.1, use the new values statement to overcome the error. If you are using an older release, declare a cursor ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.