For migration to be possible, the HSMS administrator must create a migration archive. The system migration archive must be created as a public archive with write access (USER-ACCESS=*ALL-USERS and ACCESS=*WRITE) if nonprivileged users are also to use this archive for migration.
The default system archive is assigned globally for migration by means of:
//MODIFY-HSMS-PARAMETERS - // DEFAULT-HSMS-STORAGE=*PAR(SYSMIGRATE=<archive name>)
A different pubset-specific migration archive can be assigned by means of
//MODIFY-PUBSET-PARAMETERS - // STORAGE-LEVEL=*S0(SYSMIGRATE=<archive name>)
If SM pubsets are involved in the migration processing, the HSMS administrator must define default system archives for each SM pubset for which migration is permitted. The HSMS administrator can do this either during the definition of the SM pubset with the HSMS statement CREATE-SM-PUBSET-PARAMETERS or later by modifying the SM pubset parameters with the HSMS statement MODIFY-SM-PUBSET-PARAMETERS.
If no migration archive is assigned globally (SYSMIGRATE=*UNDEFINED), migration is not possible unless a pubset has explicitly been assigned a migration archive, since recourse to a global default setting is not possible in this case.