If existing archive directories are not local for the future SM pubset, a number of operations are necessary to convert the environment of the SM pubset before the pubset itself is converted.
If part of the future SM pubset uses a shared backup or migration archive, that archive can continue to be used for that part of the pubset; for the rest of the SM pubsets, the following procedure must then be followed.
1st step: converting the migration archive
Before creating the SM pubset, all the migrated files concerned must be saved:
//SELECT-FILE-NAMES FILE-NAMES=..., - // SELECT-FROM=*CATALOG(SUPPORT=*PUBLIC-DISK( - // STORAGE-TYPE=*PUBLIC-SPACE),STORAGE-LEVEL=(*S1,*S2)), - // OUTPUT=*SELECT-LIST
Following this, a new backup archive must be created with a new archive directory:
//BACKUP-FILES FILE-NAMES=*SELECTED, - // SELECT-FILES=*ALL-FILES, - // NEW-FILE-NAMES=*BY-RULE(NEW-CATALOG-ID=...), - // SAVE-OPTIONS=*PARAMETERS(SAVE-DATA=*S2-S1-S0), - // ARCHIVE-NAME=...
Now the SM pubset can be created using DMS resources. The archive directory is used must then be transferred to the SM pubset.
The SM pubset is converted when the above-mentioned archive directory is used for the system backup archive. The migration archive is defined with a new archive directory. The new migration archive is updated with the HSMS statement REPAIR-CATALOG-BY-RESTORE.
2nd step: copying the save files to the SM pubset environment
After defining the SM pubset environment (with the new archive definitions), the user can copy the save files from the SF environment to the SM pubset environment using the HSMS statement COPY-SAVE-FILE.
For backup and long-term archives it is not always necessary to copy all the save files from the host to the SM pubset. The user can still execute a restore from the "old" archive which is defined on the host to the SM pubset, in which case the catalog ID is renamed.