| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

JDBC driver URLs

Page history last edited by PBworks 16 years, 10 months ago

jdbc:as400 indicates that we are using the iSeries Toolbox for Java JDBC driver, which is the 100% pure Java one (the native, DRDA, driver would have jdbc:db2). On an iSeries there is only one local database, referred to by DB2 locally as *LOCAL. You can talk to other iSeries’ databases using DRDA (Distributed Relational Database Architecture) which is, effectively, how all remote DB2 connectivity works (including DB2 Connect). On the iSeries DRDA is controlled via WRKRDBDIRE which specifies for each remote iSeries whether you want to use SNA or TCP/IP to talk to it. If you use jdbc:db2 you can leverage all this. If you use jdbc:as400 you simply specify the TCP/IP host name of the remote system – SNA is not supported and WRKRDBDIRE is ignored; in this case, the local system would be referred to as localhost or by its TCP/IP name.

 

Here is some example JDBC code showing DB2 access using native (idb2) and Toolbox (as400) JDBC drivers plus the 100% pure Java DB2 Connect JDBC driver (db2jcc) and the traditional DB2 Connect JDBC driver (multidb2), which last won't run on the iSeries as it requires the DB2 Connect client installed.

Comments (0)

You don't have permission to comment on this page.