With the //COPY-PUBSET and //DUMP-PUBSET statements, a save run is automatically initiated for each disk of the pubset. The consistency of the disks and their membership of the pubset is guaranteed by the time stamp. The user must make sure that all disks are attached and accessible when processing begins so that all disks of the pubset are saved with a consistent status.
During saving, MTC from the same save run which have already been used are protected against overwriting. If there are several save runs, the MTC can only be protected against overwriting during these runs if RETENTION-PERIOD > 1 is specified.
If unrecoverable errors occur on the output device during a save run, the save can only be completed correctly on an alternate volume.
In a restoration run (//RELOAD-DISK), FDDRL ensures that only MTC with the correct save version of a disk are used for restoration.
In a restoration run (//RELOAD-DISK and //COPY-DISK, //COPY-PUBSET with ACTION=*RESTORE), permanent errors on the input device can only be skipped within the context of indispensable restrictions and with loss of the affected data.
Error messages during tape processing may not necessarily be due to faulty tape cartridges. The errors could, for example, be caused by dirty read/write heads on the MTC device. In any event, an increased incidence of errors should certainly be investigated. Only MTC of the highest quality should be used for save runs.