This section lists unsupported drivers of interest and discusses how to assess the feasibility of using unsupported third-party JDBC drivers with this product.
Table 15-31 Settings for IBM Toolbox for Java/JTOpen
If you use the IBM Toolbox for Java/JTOpen driver, you must manually enter values for the JDBC Driver Class Name and Authentication Context parameters. The settings are not automatically populated. See Third-Party JDBC Driver Class Name and Authentication Context.
The Driver for JDBC might not interoperate with all third-party JDBC drivers. If you use an unsupported third-party JDBC driver, it must meet the following requirements:
Support required metadata methods
For a current list of the required and optional java.sql.DatabaseMetaData method calls that the Driver for JDBC makes, see Section D.0, java.sql.DatabaseMetaData Methods.
Support other required JDBC methods
For a list of required JDBC methods that the Driver for JDBC uses, refer to Section E.0, JDBC Interface Methods. You can use this list in collaboration with third-party driver documentation to identify potential incompatibilities.
Because the Driver for JDBC is directly dependent upon third-party JDBC driver implementations, bugs in those implementations might cause this product to malfunction.
To assist you in debugging third-party JDBC drivers, the Driver for JDBC supports the following:
Tracing at the JDBC API level (level 6)
Third-party JDBC driver (level 7) tracing
Stored procedure or function support is a likely point of failure.
You’ll probably need to write a custom driver descriptor file.
Specifically, you’ll need to categorize error codes and SQL states for the third-party driver that you are using.