During their year end testing with future date, the customer created Archvol container files on disk which MERGE does not process as their time stamp has a future date.
How to Merge an Archvol with future date?
Release: SMDI3900200-12.5-Disk-Backup and Restore-for z/OS
MERGE needs to be started with a future date set to any date after the archvol date, e.g. via IBM HourGlass for z/OS.
With a start date in the job card larger than the creation date of the container, the MERGE from DASD to TAPE will run.
After this, restoring the file will work and a later TAPE to TAPE MERGE will also work without a future date set.
The archive and expiration date of the contained files remain untouched.
In the beginning of the MERGE process, MERGE stumps the current date/time, and later compares that date/time to the Archvol date/time.
If the current date/time is less than that of theArchvol, then the Archvol is considered 'new', and the Archvol is bypassed with message 4012:
ADSDM219 4012 ARCHIVE VOLUME RECORD (arckey) HAS CHANGED SINCE MERGE STARTED. VOLUME CANNOT BE PROCESSED
ADSDM219 4012 DATA SETS ON ARCHIVE VOLUME arckey HAVE BEEN BYPASSED
This was designed to avoid selecting and Archvols created while MERGE was running.
The 'DATE=' parm in the MERGE command statement is referenced by the data expiration processing and unfortunately it is not used to override the system date,
even with 'INCLUDE', since the data/time is check before any of the command parameters are processed, the Archvol has already been bypassed.