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

With the z/OS Application Connectivity to DB2 for z/OS feature that provides DB2 universal
Driver type 4 connectivity, the use of a gateway DB2 is avoided and a 73% increase in
throughput on the WAS LPAR is realized, see Figure 7-7.
WebSphere
V502
servlet
WebSphere
V502
servlet
WebSphere z/OS - DB2 z/OS V8 - Servlet workload
JCC type 2/Gateway DB2 vs. JCC type 4
z/OS 1.3 z/OS 1.3
JCC
T2
1.8.36
JCC
T4
1.8.36
DB2 V8
for z/OS
D
D
F
D DB2 V8
D for z/OS
F
z/OS 1.3 z/OS 1.3
D
D
F
DB2 V8
for z/OS
Figure 7-7 DB2 Universal Type 2 Driver - Gateway DB2 vs. DB2 Universal Type 4 Driver
DB2 Universal Type 2 Driver vs. DB2 Universal Type 4 Driver - Local environment
In Figure 7-8 we compare the JCC Type 2 and Type 4 Driver in a local environment. The
intention is to demonstrate the difference in performance between the Type 2 and Type 4
Driver in a local environment in the same LPAR as DB2.
Since the WebSphere Application Server is local to the DBMS (same LPAR), the Type 2
Driver can do “native” calls to DB2; this configuration normally provides the best performance.
Your Java application that is running under the control of WAS can talk to DB2 through the
Type 2 JDBC Driver, and a local RRS attachment.
Using the Type 4 Driver in this configuration is not a recommended setup for a production
environment, since all SQL requests go through DRDA over TCP/IP (so through the TCP/IP
stack) into DB2’s DDF address space. Even though DRDA is a very efficient database
communication protocol, it is normally more expensive than going through the local RRS
attachment as will become clear from this test case.
Trans/sec - higher is better
500
400
300
200
100
73 %
14 %
0
WebSphere LPAR
Remote DB2
JCC type2/DB2
JCC type 4
Chapter 7. Networking and e-business 295