By default, ARCHIVE creates a new save version for each save run. However, it is also possible to extend (continue) an already existing save version, thereby making better use of the volume containing the save data.
The continuation of a save version is initiated via the CONTINUE operand of the EXPORT and SAVE statements. Whenever a save version is continued, the last volume of this version is always requested. The new files or job variables are written after the last file or job variable.
This volume can be specified in the CONTINUE operand in several ways:
When working with a directory file, it is sufficient to specify the svid. ARCHIVE determines the last volume with the aid of the directory file, and requests it.
If the VSN is specified (
vsn,...), ARCHIVE determines the save version once the volume has been read.
If you specify several VSNs and are using a directory file, ARCHIVE checks whether all volumes belong to the same save version; if not, the run is aborted.If the save version and VSNs are entered, ARCHIVE checks the consistency of the entries.
The volumes to be used when the last volume of the save version to be continued is full are specified via the VOLUME operand, i.e. taken by default from the volume pool in the case of a save run. The last volume may not be specified here.
If a directory file is being used, ARCHIVE does not save those files which have already been saved in the save version to be continued or in a later one. ARCHIVE lists these files in the report. This ensures that a file is not contained several times in the same save version, and that the files read in a subsequent RESTORE/IMPORT run reflect the most up-to-date status.
In runs without a directory file, it is the user's responsibility to ensure that the same save version does not contain multiple copies of files. Otherwise it is impossible to tell in a subsequent RESTORE/IMPORT run which version of the file is actually to be restored or imported.
The continuation of save versions is thus not suitable for saving different versions of the same file.
When save versions are continued, their original expiration data is retained.
Example
If the following entries are made, ARCHIVE may save the same file twice, even though a directory is being used.
FILES NAME=FILE1 FILES FROM=SV,(MBK001) SAVE DIR=directory,VOLUME=MBK002,...
Reason: if FILE1 was also on the specified tape (MBK001), then it will be saved twice to MBK002.
This duplicate saving of files can be avoided with the aid of the CONTINUE operand:
FILES NAME=FILE1 SAVE DIR=DIRECTORY,VOLUME=MBK002,... FILES FROM=SV,(MBK001) SAVE DIR=directory,CONTINUE=(MBK002),...
This statement sequence causes the save data on MBK002 to be brought up to date: the files on MBK001 are saved to MBK002 only if no (more recent) file with the same name has been saved from disk.