Are CA View and CA Deliver compatible with Extended Address Volume (EAV) devices?

Products

• Deliver
• View

Issue/Introduction

This document discusses the compatibility of CA View and CA Deliver with Extended Address Volumes (EAV) devices.

Environment

View, Deliver, 14.0, z/OS

Cause

Compatibility

Resolution

- Extended Address Volume (EAV) devices are supported by all levels of CA View and CA Deliver.

- EAV allows for devices with more than 64K-1 Cylinders, but z/OS does not allow physical sequential data sets beyond the 64K-1 cylinder boundary.

- For View/Deliver database data sets that are 4,369 or fewer cylinders, the data sets are to be allocated as an IBM direct access data set.

- For data sets that are more than 4,369 cylinders, the data sets are to be allocated as physical sequential data sets due to IBM restrictions.

View/Deliver provides an optional ABOVE parameter, that can be specified on the ADDDS control statement used to allocate a DATA or INDEX extent. 

- ABOVE indicates that the data set being added to the database can be allocated above the 64K cylinder line on a 3390-A device. Data sets that are allocated above the 64K cylinder line are allocated in increments of 21 cylinders so the final data set allocation is rounded up to the next multiple of 21 cylinders.   

*NOTE* 
The first extent of the index and the database must be placed on separate dedicated volumes because the RESERVE processing uses the dataset name and volume of the first extent to serialize all accesses.

The Deliver Checkpoint dataset is not compatible with Extended Address Volumes (EAV) devices

Additional Information

For more detailed information on allocating database and index extents, please refer to the following areas of documentation:

View - SARDBASE ADDDS control statement details.

Deliver - RMODBASE ADDDDS control statement details.