Allow RESTORE with REPLACEUNCONDITIONAL of source single-volume sequential to multi-volume pre-allocated target

RESTORE of Non-VSAM data set causes diagnostic:

ADR380E (002)-FRLBO(19), DATA SET USERID.TEST.SEQ1 NOT PROCESSED, 80

Data set was allocated with DATACLAS allowing 20 candidate DASD volumes, of which 1 was used to contain a number of data extents. In the catalog entry the remaining 19 volumes are still '*' candidates.

In ISMF this data set has the multivolume field as YES, probably due to catalog entry?

Data set was then DUMPed using DFSMSdss to archive data set. It appears that DSS classifies this data set as 'single volume' due to it only having extents on the first volume?

Subsequent to the DUMP this data set either has data appended to it, or it is rewritten from the start, it does not matter which. The end result is that the 16 physical extent limit is reached on the first volume, and the data set is extended to the next '*' candidate volume, so that now the data set is truly multivolume having physical extents on 2 or more DASD volumes.

Now when a DSS RESTORE is attempted from the archive data set with REPLACE, to overwrite the target data set currently on DASD, DSS issues the ADR380E rsn 80 diagnostic.

DSS appears to be saying that the source data set in the archive is 'single volume', or only having extents on a single volume, when it was DUMPed, and there is a mismatch with the target data set which is now truly multivolume and occupies 2 or more volumes.

It appears that DSS is not able to make use of the existing target extents on DASD, either on 1 or 2 or more volumes, to RESTORE the data set and then either retain any left over target extents as free space or release unneeded extents if they exist.

It appears that DSS will not in this case delete the target data set itself and allocate it as new, and there is no keyword or PATCH to change this behaviour?

It appears that DSS will not attempt any sort of RESTORE in this case and will instead issue ADR380E for the user to correct the mismatch.

Not knowing which data sets may have extended to 2 or more volumes since the DUMP was taken would require pre-deleting any multivolume Non-VSAM sequential data sets prior to the RESTORE.

Please provide a keyword or PATCH to allow use of the target data set's pre-allocated extents, otherwise allow DSS to DELETE the target data set and allocate new using the source attributes.