S837-08 while creating a multi-volume Archvol in ARCHIVE to DASD

Document ID : KB000003911
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

The customer archives data sets to disk by selecting a SMS Storagegroup

SCAN REALVOLS 
SELECT SGNAME=SGB1    
ARCHIVE DISP=RECAT   

Sometimes the Storagegroup contains a large data set for which the Archive fails with message -

ADSTH011 2932 NO VOLUME WAS FOUND IN THE DISK POOL TO SATISFY THE    
MINIMUM ALLOCATION REQUIREMENTS OF *********** BYTES.

The customer does not want to treat these large data sets in a special way, e.g. to Archive them directly to tape. 

They use SMS to manage the Archvols allocation and DVC is set in the related SMS Dataclass to allow multi-volume allocation. The SMS Storagegroup for the 
Archvols consists of 5 volumes with 33390 cylinders each, so in total 166950 cyls (with 45275 cyls allocated and 121675 cyls available as a sample). 

But although there is enough space for the allocation of a multi-volume Archvol for a file of 22750 cyls, the allocation fails with S837-08.

Cause:

The problem is caused because a data set cannot exceed 65535 tracks = 4369 cyls per volume. The concerned data set has 22750 cyls which would need to be spread over 6 volumes, but the pool has only 5 volumes.

Resolution:

As a workaround the customer can add 1 or 2 more volumes to the pool or consider to use compression with DCDATACP set to Y.