Parallel Access Volumes (PAV) allow z/OS to start more than 1 I/O to each System z 3390 image. This way most queueing can be eliminated, and overall I/O throughput can be improved significantly.

PAV uses ‘alias’ addresses are used to start the additional I/Os. The ‘alias’ addresses need to be configured by the installation. Two different modes are supported in z/OS:

  • With Static PAVs the alias assignment is fixed, so you need to manually assign a certain number of aliases to each volume for which you want to reduce queueing.
  • With Dynamic PAVs the alias assignment will be more dynamic, you simply assign a pool of addresses to each LCU. z/OS will assign the aliases where they are most useful to reduce queuing and to help meet the service objectives of your installation.
  • With HyperPAV the alias assignment occurs for each individual I/O request for each LPAR accessing the Disk Subsystem. This mechanism is by far the most efficient.

zOS Disk Parallel Access Volumes PAV

When HyperPAV cannot be used, dynamic PAV (shown in the image) is the preferred option to use, as it will automate the alias management.

You do need to know how many aliases to assign to each volume. How many are needed depends mostly on the activity of the volume, where larger volumes (“3390 Model 54”) are more likely to show a high I/O rate. IntelliMagic Vision for z/OS provides recommendations on the number of aliases required for both HyperPAV and Dynamic PAV configurations.

Related Content

Video

IntelliMagic Vision for z/OS Disk Overview

Discover how IntelliMagic Vision can optimize your z/OS disk environment and enhance your understanding of the internals of your environment.

Watch video
Video

Global Mirror RPO Spikes

This video will show you how IntelliMagic Vision can be used to provide visibility to the status of Global Mirror replication in a Globally Disbursed Parallel Sysplex environment.

Watch video
Video

High z/OS Disk Connect Time

By drilling down to specific volumes and consulting change logs, it is easy to determine the root cause of high z/OS Connect time as coming from a newly released SQL query.

Watch video

Go to Resources