Introduction › Components › ODBC and JDBC Drivers › JDBC Driver

JDBC Driver

You can use the JDBC driver on Java 1.6 (or later) platforms, including those on Windows, z/OS, Linux, and UNIX. The JDBC driver implements the JDBC 4.0 specification.

There are four types of JDBC drivers that differ in the way they communicate with the database and whether they use native code on the client platform:

• Type 1 JDBC driver—Uses an ODBC driver to communicate with the database. ODBC drivers are always implemented in native code. The JDBC-ODBC Bridge is a basic Type 1 driver that is rarely used now that database specific drivers are available.
• Type 2 JDBC driver—Invokes the native client interface to communicate with the database.
• Type 3 JDBC driver—Uses a generic network protocol to communicate with a middleware server that invokes the native client interface to communicate with the database. It uses no native code on the client platform.
• Type 4 JDBC driver—Communicates directly with the database using its proprietary protocol. It uses no native code on the client platform.

The CA IDMS Server JDBC driver is a universal driver that can function as a Type 2, 3, or 4 driver on supported platforms depending only on the connection parameters specified.

The JDBC driver can be used as a Type 2 driver on Windows and z/OS. It calls the native SQL client interface, which can use CAICCI to communicate with any supported release of CA IDMS running on z/OS or VSE. CAICCI uses TCP/IP from Windows and cross memory services on z/OS.

The JDBC driver can be used as a Type 3 driver on any Java platform. It uses TCP/IP to communicate with the JDBC server, which can run on any Java platform. When the JDBC server runs on Windows or z/OS, it can invoke the native SQL client interface and CAICCI to communicate with any supported release of CA IDMS running on z/OS or VSE. The JDBC server can use TCP/IP from any Java platform to communicate directly with CA IDMS r16 SP2 or later running on z/OS, VSE, or z/VM.

The JDBC driver can be used as a Type 4 driver on any Java platform. It uses TCP/IP to communicate directly with CA IDMS r16 SP2 or later running on z/OS, VSE, or z/VM.