When migrating files from S1 to S2, the load on storage level S1 is reduced even further by deleting the save files on S1 after migration. This, however, increases access time and implicit recall in interactive mode is only possible during tape sessions.
The catalog entry of the migrated file is updated, i.e. the entries for DEVICE-TYPE and STORAGE-LEVEL are modified (PUB/S2).
Files are migrated to S2 via the following HSMS statement:
//MIGRATE-FILES FROM-STORAGE=*S1-STORAGE-LEVEL(..., TO-STORAGE=*S2-STORAGE-LEVEL,...)
In doing this, the HSMS administrator has the same options as for migration from S1 to S1.
In particular, we recommend migrating files via MINIMUM-DAYS-ON-S1, since the probability that a file will still be required for processing decreases over time.
Regardless of the settings of the SAVE-FILE-PROCESSING option at file creation on S1 level, this file can be migrated from S1 to S2 with any setting of the SAVE-FILE-PROCESSING option.