Moving save files with MOVE-SAVE-FILE is not possible for version backups. However, function of reorganizing version backups provides possibility of changing storage of the save files being reorganized. By means of the statement REORGANIZE-VERSION-BACKUP it is possible to specify storage to which save files will be copied. Since version 12.0D, FORCED-MOVE execution mode for REORGANIZE-VERSION-BACKUP has been added to move save files irrespective of existence of obsolete file versions.
TO-STORAGE = *S2-STORAGE-LEVEL(...)
Save files to be reorganized can be selected by their creation date:
SAVE-FILE-ID = *BY-ATTRIBUTES(CREATED-BEFORE=
A save version created by a reorganization run receives the current timestamp as a SVID. The functionality of the REORGANIZE-VERSION-BACKUP statement combines that of several statements:
- copying of several save files with selecting only valid file versions to a given storage (COPY-SAVE-FILE)
- subsequent purge of original save files from the archive.
In case of reorganization from disk to S2-level, each save file on disk after reorganization will be presented as save version with current date as a svid in a new save file on the tape. When reorganizing to disc storages all the save versions/save files are copied to separate save files on the disc storage. New save files are created: no continuation of save files is provided during the reorganization.
The retention period of save files created by reorganization is taken from the version backup archive attributes.