Migration is restricted to BS2000 files on shared volumes. It is the process of moving inactive data from the processing level to a background level. The migrated data is moved to a migration archive and the storage space it occupied at the processing level is released. However, migrated files retain their catalog entry at the processing level and can continue to be addressed via this entry. In particular, the data is recalled implicitly (i.e. automatically) to the processing level when an access attempt is made by the BS2000 Data Management System.
The migration function is available to all users if the archive is created accordingly. However, the HSMS administrator can restrict its usage.
Migration can be carried out only to pubsets that have been taken under HSMS management.
Files which are stored on a Net-Storage volume assigned to the pubset cannot be migrated.
Files which are stored on a disk storage system and are mirrored remotely in another disk storage system (e.g. Symmetrix disks mirrored with SRDF) should not be migrated if the remote host is unable to access the S2 processing level.
You can also use the HSMS statement MIGRATE-FILES to migrate files of which you are the co-owner (see the “SECOS” manual [16]).
When a MIGRATE-FILES statement is issued on a host that manages both SF and
SM pubsets, only objects that are located either on an SF or on and SM pubset can be migrated at any one time. Furthermore, when migrating objects to SM pubsets, only objects of an SM pubsets can be processed in each run.
Migration control and migration archive management by the HSMS administrator are described in section "Migration control and management of migration archives".
An attempt to access a migrated file causes a DMS error
if HSMS is not available on the system
if an implicit recall is prohibited
if an implicit recall failed.