19.06.2013 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 8. Data sharing enhancements<br />

8<br />

<strong>DB2</strong> data sharing allows you the highest level of scalability, per<strong>for</strong>mance, and continuous<br />

availability by taking advantage of the z Parallel Sysplex technology to provide applications<br />

with full concurrent read and write access to shared <strong>DB2</strong> data. For an introduction, refer to<br />

<strong>DB2</strong> <strong>for</strong> z/<strong>OS</strong>: Data Sharing in a Nutshell, SG24-7322.<br />

<strong>DB2</strong> data sharing was introduced in 1994 with <strong>DB2</strong> V4, and continues to evolve exploiting key<br />

functions of the <strong>IBM</strong> System z servers.<br />

Data sharing <strong>DB2</strong> V8 provides a number of significant enhancements to improve availability,<br />

per<strong>for</strong>mance and usability of <strong>DB2</strong> data sharing:<br />

► CF request batching: This enhancement utilizes new functionality in z/<strong>OS</strong> 1.4 and CF<br />

level 12 to enable <strong>DB2</strong> to:<br />

– Register and write multiple pages to a group buffer pool in a single request<br />

– Read multiple pages from a group buffer pool <strong>for</strong> castout processing<br />

This reduces the amount of traffic to and from the coupling facility <strong>for</strong> writes to group buffer<br />

pools and reads <strong>for</strong> castout processing, thus reducing the data sharing overhead insert,<br />

update and delete-intensive workloads.<br />

► Locking protocol level 2: Protocol Level 2 remaps IX parent L-locks from XES-X to<br />

XES-S locks. Data sharing locking per<strong>for</strong>mance benefits because this allows IX and IS<br />

parent global L-locks to be granted without invoking global lock contention processing to<br />

determine that the new IX or IS lock is compatible with existing IX or IS locks.<br />

► Change to IMMEDWRITE default BIND option: In prior releases of <strong>DB2</strong>, any remaining<br />

changed pages in a data sharing environment are written to the group buffer pool during<br />

phase 2 of commit, unless otherwise specified by the IMMEDWRITE BIND parameter.<br />

This enhancement changes the default processing to write changed pages during commit<br />

phase 1. <strong>DB2</strong> will no longer write changed pages during phase 2 of commit processing.<br />

► <strong>DB2</strong> I/O CI limit removed: Prior to <strong>DB2</strong> V8, <strong>DB2</strong> did not schedule a single I/O <strong>for</strong> a data<br />

set with CIs that span a range of more than 180 CIs. V8 removes this limit <strong>for</strong> list prefetch<br />

and castout I/O requests. This is true in CM and NFM.<br />

► Miscellaneous items:<br />

© Copyright <strong>IBM</strong> Corp. 2005. All rights reserved. 319

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!