DB2 Universal JDBC Driver support
This article lists the support details for using the DB2® Universal JDBC Driver with WebSphere® Application Server for z/OS®.
- The z/OS Application Connectivity to DB2 for z/OS feature
that provides DB2 Universal JDBC Driver Type 4 connectivity.
This DB2 Universal JDBC Drive can be invoked only
as a type 4 driver for z/OS. As a type 4 driver, it uses
a communication protocol to communicate requests from a z/OS application
to a remote DB2 database.
When you install and configure this driver for WebSphere Application Server for z/OS, it permits your applications to use JDBC or Container Managed Persistence (CMP) support to access backend DB2 databases (DB2 V7 and up) residing on z/OS at any location. All global transactions are handled as Java™ Platform Enterprise Edition (Java EE) XA transactions.
- The DB2 Universal JDBC Driver in DB2 UDB
for z/OS Version 8. This driver provides both Type
2 and Type 4 support.
Type 4 driver support uses a communication protocol to communicate requests from a z/OS application to a remote DB2 database. This driver supports using Java EE XA transaction processing to process global transactions.
Type 2 driver support uses local API protocol to communicate requests from a z/OS application to a target DB2 running on the same z/OS system image as the application. When the Type 2 driver is used under z/OS, the driver supports the use of z/OS Resource Recovery Services (RRS) to coordinate global transactions across multiple resource manages using 2-phase commit processing.
When you install and configure this version of the driver, your applications can use JDBC or CMP support to access backend DB2 databases (DB2 V7 and up). These databases can reside on the same z/OS system image, or on a different z/OS system image. depending on the driver type used. Type 2 driver handles all global transactions as RRS-coordinated global transactions.
- The DB2 Universal JDBC Driver Provider by APAR PQ80841
on DB2 UDB for OS/390® and z/OS Version
7. This version provides both driver Type 2 and driver Type 4 support.
Type 4 driver support uses a communication protocol to communicate requests from a z/OS application to a remote DB2 database. This driver supports using Java EE XA transaction processing to process global transactions.
Type 2 driver support uses local API protocol to communicate requests from a z/OS application to a target DB2 running on the same z/OS system image as the application. When the Type 2 driver is used under z/OS, the driver supports the use of z/OS Resource Recovery Services (RRS) to coordinate global transactions across multiple resource manages using 2-phase commit processing.
When you install and configure this version of the driver, your applications can use JDBC or CMP support to access backend DB2 databases (DB2 V7 and up). These databases can reside on the same z/OS system image, or on a different z/OS system image, depending on the driver type used.