Data is taken during a file recall from the save file of the S1 or S2 storage level on which it was placed during the last migration, secondary migration or copy operation performed within the migration archive. This save file is registered in the localization information contained in the file’s catalog entry. Other save files in the migration archive are therefore only interpreted during a recall as being repositories for the data of migrated files.
If the save file registered in the localization information of a migrated file’s catalog entry does not exist, or the save file on the respective storage level no longer exists, it constitutes a migration file inconsistency. This also means that all files are inconsistent because their respective catalog entries contain no localization information.
Inconsistencies in migrated files can be displayed with the aid of the SHOW-PUBSET-USAGE statement’s INFORMATION=*MIGRATION-EVALUATION operand. This display function also takes into account the above-mentioned definition of inconsistency. This means that operator error may cause the system to indicate that a file is inconsistent when that file is still capable of being recalled. This situation can arise if the save file registered in the catalog entry exists but is no longer registered in the migration archive.
The HSMS statements REPAIR-CATALOG-BY-EXCHANGE and REPAIR-CATALOG-BY-RESTORE provide a means of correcting inconsistencies in migrated files.