EOV Volumes Processing

book

Article ID: 130702

calendar_today

Updated On:

Products

CA Allocate DASD Space and Placement

Issue/Introduction

We have a test job that allocates 21,000 cyl primary and 500 cyl secondary. 
When the dataset extends to another volume, only the secondaries are used. 
Why would CA Allocate not use the primary allocation of 21,000 cyl when extending to another volume? 

Why does CA Allocate not use the primary allocation when extending a non-VSAM to another volume? 

Environment

Release:
Component: ALLOC

Resolution

CA Allocate [VAM] is simply allowing what the normal IBM processes are.
  
When another volume is added to a non-VSAM allocation in EOV:
The first (and following) extents on the next volume is the SECONDARY value.
  
When another volume is added to a VSAM allocation in EOV_VSAM:
The first extent on the next volume is the PRIMARY value.