11.01.2013 Views

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - IBM Redbooks

ABCs of z/OS System Programming Volume 3 - 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.

Large volume support design considerations<br />

Benefits <strong>of</strong> using large volumes can be briefly summarized as follows:<br />

► They reduce storage management tasks by allowing you to define and manage smaller<br />

configurations.<br />

► They reduce the number <strong>of</strong> multivolume data sets you have to manage.<br />

► They relieve architectural constraints by allowing you to address more data within the<br />

existing 64K subchannel number limit.<br />

The size <strong>of</strong> the logical volume defined does not have an impact on the performance <strong>of</strong> the<br />

ESS subsystem. The ESS does not serialize I/O on the basis <strong>of</strong> logical devices, so an<br />

increase in the logical volume size does not affect the ESS backend performance. Host<br />

operating systems, on the other hand, serialize I/Os against devices. As more data sets<br />

reside on a single volume, there will be greater I/O contention accessing the device. With<br />

large volume support, it is more important than ever to try to minimize contention on the<br />

logical device level. To avoid potential I/O bottlenecks on devices:<br />

► Exploit the use <strong>of</strong> Parallel Access <strong>Volume</strong>s to reduce I<strong>OS</strong> queuing on the system level.<br />

► Eliminate unnecessary reserves by using WLM in goal mode.<br />

► Multiple allegiance will automatically reduce queuing on sharing systems.<br />

Parallel Access <strong>Volume</strong> (PAV) support is <strong>of</strong> key importance when implementing large<br />

volumes. PAV enables one MVS system to initiate multiple I/Os to a device concurrently. This<br />

keeps I<strong>OS</strong>Q times down and performance up even with many active data sets on the same<br />

volume. PAV is a practical “must” with large volumes. We discourage you from using large<br />

volumes without PAV. In particular, we recommend the use <strong>of</strong> dynamic PAV and HyperPAV.<br />

As the volume sizes grow larger, more data and data sets will reside on a single S/390 device<br />

address. Thus, the larger the volume, the greater the multi-system performance impact will be<br />

<strong>of</strong> serializing volumes with RESERVE processing. You need to exploit a GRS Star<br />

configuration and convert all RESERVE's possible into system ENQ requests.<br />

56 <strong>ABCs</strong> <strong>of</strong> z/<strong>OS</strong> <strong>System</strong> <strong>Programming</strong> <strong>Volume</strong> 3

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

Saved successfully!

Ooh no, something went wrong!