I ran a job which moved ARCHIVEd datasets from ML0 to ML1. Due to the amount of data (> 35GB), the job took more than the default time and eventually abend with S322 (not enough time).
One of the ARCHVOLS which was being written is now flagged as 'OPEN' and when I run my MERGE job which migrates ML1 datasets to ML2, I get the message:
ADSDM218 3778 ARCHVOLS RECORD (nnnnn) SELECTED FOR MERGE PROCESSING IS MARKED AS OPEN, THEREFORE, THIS RECORD IS BEING BYPASSED.
Is there a way to 'close' this ARCHVOLS record and make it valid for the MERGE process?
When a process fails (or is cancelled) while writing to an output volume, the ARCHVOL is marked as OPEN and will remain in that state for the next two (2) days grace period.
The Merge job that you are running should simply bypass the volume and continue processing any other volumes in the list. After two (2) days the volume that was open at the time of the failure (or cancellation) will be picked up and processed normally.
To circumvent the two day grace period, you can run the IXUPDATE RESET command with these parms:
This will turn-off the OPEN flag so the Archvols volume can be used for Merge, Purge or IXMAINT.
Release: SMDI3900200-12.5-Disk-Backup and Restore-for z/OS