z/OS: DB2 Universal JDBC Driver support

z/OS: DB2 Universal JDBC Driver support</h2> This article lists the support details for using the DB2 Universal JDBC Driver with WebSphere Application Server for z/OS . WAS for z/OS supports the DB2 Universal JDBC Driver. The capabilities available depend on the DB2 Universal JDBC Driver that we installed as follows: <ul> <li>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 we install and configure this driver for WAS for z/OS, it permits the 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 EE XA transactions. <li>The DB2 Universal JDBC Driver in DB2 UDB for z/OS v8. 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 (<a href="http://setgetweb.com/p/WAS9/ae/was417.html">RRS</a>) to coordinate <a href="http://setgetweb.com/p/WAS9/ae/was716.html">global transactions</a> across multiple resource manages using 2-phase commit processing. When we install and configure this version of the driver, the 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 <a href="http://setgetweb.com/p/WAS9/ae/was716.html">global transactions</a> as RRS-coordinated <a href="http://setgetweb.com/p/WAS9/ae/was716.html">global transactions</a>. <li>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 <a href="http://setgetweb.com/p/WAS9/ae/was716.html">global transactions</a>. 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 <a href="http://setgetweb.com/p/WAS9/ae/was417.html">Resource Recovery Services</a> (<a href="http://setgetweb.com/p/WAS9/ae/was417.html">RRS</a>) to coordinate <a href="http://setgetweb.com/p/WAS9/ae/was716.html">global transactions</a> across multiple resource manages using 2-phase commit processing. When we install and configure this version of the driver, the 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. </ul> <li><a href="was1613.html"> Data source minimum required settings, by vendor</a> </body> </html>