Save files containing invalid files on level S2 can also be copied by using the COPY-SAVE-FILE statement:
//COPY-SAVE-FILE ...,MIGRATION-STATE=*MIGRATED-FILE
In this case as well, only valid files are accepted.
The original save file is not automatically deleted after copying; it must be released by means of //MODIFY-ARCHIVE. It is also recommended not to archive save files with the same content over a longer period of time. Older save files should in this case be deleted as soon as possible, otherwise redundant save versions of the migrated files will remain in one and the same save file in subsequent reorganizations with //MIGRATE-FILES.
During a reorganization carried out using //COPY-SAVE-FILE, only a single save version is created in the target save file, even if the original save file contains more than one save version. The effect of this is to reduce the size of the directory file associated with the migration archive and to reduce the subsequent processing time.
If a backup copy of a save file in a migration archive was created, the data is recalled from the copy in the following cases:
Recall from the last copy by an HSMS operation, regardless of the storage level on which it resides
Implicit recall from the last copy on the storage level indicated in the catalog entry for the file.
Of course, save files on S1 can likewise be copied via //COPY-SAVE-FILE.
But in any case, reorganization using the MIGRATE-FILES statement provides better options for control and selection.