DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

or net driver, but if you are not using it already, you are strongly encouraged to use the
Type 4 Driver instead.
► Type 4
A Type 4 Driver is fully written in Java, and provides remote connectivity using DRDA
within IBM products. As the driver is fully written in Java, it can be ported to any platform
that supports that DBMS protocol without change, thus allowing applications to also use it
across platforms without change.
This driver type has been implemented through the IBM DB2 Universal Driver for SQLJ
and JDBC. This driver is also known as the DB2 Universal Driver for Java Common
Connectivity or JCC. In addition, the Universal Driver also provides Type 2 connectivity.
For more information on these Drivers, see the book DB2 for z/OS and OS/390: Ready for
Java, SG24-6435.
The DB2 Universal Driver for SQLJ and JDBC is an entirely new driver, rather than a
follow-on to any other DB2 JDBC drivers. The DB2 Universal Driver has the following
advantages over the previous solutions:
► One single driver for the Unix, Windows, and z/OS platforms, improving portability and
consistent behavior of applications.
► Improved integration with DB2.
► Type 4 Driver functionality for thin clients, as well as Type 2 functionality.
► Easier installation and deployment. As a Type 4 Driver is completely written in Java, it is
easy to deploy; you only have to ship the jar files containing the Driver code to the required
machine, change the classpath, and you are done. In addition, the use of a Type 4 Driver
does not require any setup in DB2, such as cataloging entries in the Database, Node, and
DCS directories. For DB2 on z/OS you only have to use the following URL syntax:
jdbc:db2://:/
► 100 percent Java application development process for SQLJ
► 100 percent JDBC 3.0 compliance. Since DB2 UDB V8.1.3 (FixPak 3), the Universal
Driver is JDBC 3.0 compliant. The version that is made available with z/OS is also JDBC
3.0 compliant.
► Significant performance improvements for both JDBC and SQLJ applications on the Linux,
Unix, and Windows platforms.
► Trace improvements.
In general, you should use Universal Driver type 2 connectivity for Java programs that run on
the same z/OS system as the target DB2 subsystem. Use Universal Driver type 4 connectivity
for Java programs that run on a different system from the target DB2 subsystem.
For Java applications, application connectivity from a z/OS LPAR to a remote DB2 for z/OS
system does not need a DB2 instance anymore. The z/OS Application Connectivity to DB2 for
z/OS optional feature can be installed to provide Universal Driver type 4 connectivity.
7.3.1 Performance measurement
The performance objectives were to verify that:
► The DB2 Universal JDBC type 2 Driver provides better or equivalent performance for
workloads using container managed persistence (CMP) and better performance for
traditional workloads that use the type 2 IBM DB2 App Driver.
Chapter 7. Networking and e-business 293