Download PDF - IBM Redbooks

The solution is the Hybrid DBSL, which couples the use of the new DBSL to DB2 10 for z/OS
transparently for the customer. You do not have to manually exchange DBSLs depending on
the DB2 release that is employed. As illustrated in Figure 3-3, the SAP kernel loads a DBSL
stub (delivered with the file name dbDB2sLib). Upon the first connection, this stub loads the
appropriate DBSL, which is the classic DB2 8 or 9 DBSL (named dbdb2slib9) or the new DB2
10 DBSL (named dbdb2slibx). All three files are delivered by SAP with the respective kernel
update. Therefore, customer intervention is necessary.
New DBSL
parts
old DBSL
dbdb2slib9.o
DB2 V8/9
Figure 3-3 Hybrid DBSL
The coupling to DB2 10 ensures that the new DBSL is validated with all products. The
performance has been tested with DB2 10, but you must validate the complete scenario
during testing before you migrate to DB2 10.
In addition, the concept of the hybrid DBSL is valid for the safe rollout of future DB2 releases.
3.3.3 DBA Cockpit changes
SAP kernel
DBSL stub
dbdb2slib.o
DBSL for DB2 10
� identical for 6.x/7.x �
dbdb2slibx.o
DB2 10
The rollout of DB2 10 and the hybrid DBSL leads to many changes and improvements in the
monitoring and administration infrastructure delivered with the SAP product. Some of the
improvements in the area of the DBA Planning Calendar are mentioned in 3.2.3, “Usability
and availability enhancements” on page 37.
This section shows the major monitoring and administration improvements with DB2 10.
Some of the features have also been added for previous releases of DB2. They are available
with the support packages that are necessary for DB2 10.
40 Running SAP Solutions with IBM DB2 10 for z/OS on the IBM zEnterprise System