Files which have already been recalled, overwritten or deleted can no longer be recalled and are therefore invalid in the migration archive. It is therefore necessary to reorganize the migration archive regularly to ensure that only valid files remain in the migration archive and all invalid files are deleted. Reorganizing the migration archive can also be a means of avoiding bottlenecks on volumes used for the migration archive.
However, the validity of a file is not indicated in the migration archive but must be checked on the basis of the catalog when the archive is accessed (i.e. also during reorganization). A file is “valid” if it still has a catalog entry which marks it a “migrated” file and if its CFID and version number are equivalent to those in the save file.
If the pubset catalog is unavailable at the time the check is carried out, its files are considered to be valid. During reorganization, all the files are accepted without comment, even if they are in fact invalid.
Summary of reusable storage space
When S1 is reorganized, a summary can be displayed to help the HSMS administrator. The summary shows how much storage space at S1 is occupied by save files only partially filled with valid files:
//SHOW-PUBSET-USAGE INFORMATION=*REUSABLE-S1-SPACE
For more information on this information option, see "HSMS Vol. 2” [1], HSMS statement SHOW-PUBSET-USAGE.
The HSMS administrator has four options for reorganizing the migration archive; which one is selected depends, among other things, on whether data is migrated to S1 or only to S2.