The opposite of migration, i.e. copying migrated data back to the processing level, is known as “recall”.
The number of files that can be recalled to S0 is restricted by the space allocated to the individual user IDs.
Only files cataloged as migrated files and only that status in the migration archive which matches the catalog entry (CFID and version) can be recalled. The current state of a file on the processing level is not changed by a recall.
Nonprivileged users can recall the files under their own user ID. Users can only recall files of another user ID they are co-owners of the file or the file access rights permit access for other user IDs. In particular when the recall concerns a migrated file of another user ID it should be borne in mind that this also increases the storage space occupation of this user ID.
Warning
The following file attributes are modified by a recall: CFID (coded file ID), DEVICE-TYPE, SUPPORT, VOLUME and EXTENTS. This must be taken into consideration in applications which evaluate these attributes.
HSMS offers two different options for recalling a migrated file:
recall by HSMS statement (explicit recall)
recall on access (implicit recall)