ADSDF102 4106 ADR472E (001)-NEWDS(06), UNABLE TO SELECT ..., 04

book

Article ID: 211870

calendar_today

Updated On:

Products

CA Disk Backup and Restore - MVS

Issue/Introduction

During the RESTORE of a multivolume dataset involving the  Data Mover (DFSMSDss) and a command looking like the following:

RESTORE DSN=...dsname...,                     
  NEWNAME=...new dsname...,                                       
  OUTDY=(MIGL00,MIGL04,MIGL09,MIGL14,MIGL17,MIGL19,MIGL22,MIGL28,
  MIGL30,MIGL34,MIGL39,MIGL44,MIGL47,MIGL49,MIGL42,MIGL48)                                 

It can happen to get the error: 

ADSDF102 4106 ADR472E (001)-NEWDS(06), UNABLE TO SELECT A TARGET VOLUME FOR DATA SET '...dsname...', 04 

...                                                                       
ADSDF102 4106                           ...dsname...
ADSFH112 4495 VOLUME =        IS OFFLINE OR INVALID                            
ADSME453 0732 ERROR DURING SCRATCH OF DSNAME (...dsname...)
ADSME453 0732 RESULT ....... 9                                                 
ADSME453 0732 REASON CODE... 4                                                 
ADSME453 0732 REASON........VOLUME COULD NOT BE ALLOCATED (FH112)      

and the same also using PRIALLOCY or PREALLOCY 

How to bypass this error and successfully restore the dataset?       

Environment

Release : 

Component : CA Disk Backup and Restore

Resolution

When CA DISK calls DFDSS for RESTORE, it is DFDSS that performs allocation based on space allocation recorded into the File dataset. 
In addition DFDSS always, when doing restore, consolidates data to suppress extents. In that specific case, it is IBM algorithm that is used and this can be found in the IBM documentation related to DFDSS at the link below:

Copying or restoring multivolume data sets


...

DFSMSdss does not ensure that the copied or restored data set is on the same number of volumes as the original data set, nor does DFSMSdss ensure that the copied or restored data set extents are the same as the original data set. Instead, DFSMSdss tries to allocate the new data set on as few volumes as possible. This may result in the copied or restored data set becoming a single-volume data set.

* In addition, DFSMSdss tries to allocate each volume so that all data is contained in a single primary allocation of contiguous space with few, if any, of the secondary allocations being used.

....

Based on that, it is really important that the 1st volume of the OUTDY volumes list does contain enough contiguous space to perform the Restore. This is how the error can be bypassed.