The HSMS administrator can reorganize save files at level S1 by “migrating” them from S1 to S1:
//MIGRATE-FILES FROM-STORAGE=*S1-STORAGE-LEVEL(..., TO-STORAGE=*S1-STORAGE-LEVEL,...)
In doing this, only the valid files are transferred to the new save file. If the save file was empty, i.e. if it contained only invalid files, or copies of valid files (such copies, for example, can be created with //COPY-SAVE-FILE), it is deleted. No new save file is created.
After a successful migration operation, the old save file is always deleted, regardless of the stipulated retention period.
The HSMS administrator has the following options when migrating files from S1 to S1:
He can use the MINIMUM-/MAXIMUM-DAYS-ON-S1 operand to restrict selection to save files of a certain age. For example, he can reorganize all save files which have been on level S1 for the last 30 days.
He can use MINIMUM-SIZE to restrict migration to save files of a certain minimum size.
With the UNUSED-SPACE operand the save files can be selected according to the percentage of invalid files they contain. For example, UNUSED-SPACE=60 means that only those save files which are at least 60% empty are reorganized.
When UNUSED-SPACE=100 is specified, the empty save files are deleted.RELEASE-PAGES can be used to restrict the quantity of save files to be migrated until a definable number of PAM pages has been released by reorganization (as in migration from S0).
No specific volume sets can be selected for backups, migration and reorganization on the S1 level defined by all volume sets under HSMS control.
However, the HSMS administrator can restrict the volume set usage with the following command:
/MODIFY-PUBSET-RESTRICTIONS PUBSET=<SM_pubset_catid>, - / PUBSET-TYPE=*S-M(VOL-SET=<catid_of_volume_set>, - / RESTRICTION = *NEW-FILE-ALLOCATION)
Note on reorganizing from S1 to S1 in an SM pubset environment
If the S1 level is defined by all volume sets under HSMS control, migration from S1 level to S1 can be carried out with SAVE-FILE-PROCESSING=*HSMS-V10-COMPATIBLE only in BS2000 OSD/BC V11.0A or higher.