Transfer of a user ID to another pubset

If a user ID is to be transferred to another pubset, all files and job variables of the user must be transferred to the target pubset. The migrated files of the user do not need to be recalled specially.

Activities to be executed:

/START-DIRCONV
//RENAME-CATID DIRECTORY-NAME=backup.dir (Name des SYSBACKUP-Directory)
              ,OLD-CATID=*BY-SPECIFICATION(CATID=cat-id1,USER=user-id)
              ,NEW-CATID=cat-id2
              ,NEW-DIRECTORY-NAME=new.backup.dir
//RENAME-CATID DIRECTORY-NAME=migrate.dir 
              ,OLD-CATID=*BY-SPECIFICATION(CATID=cat-id1,USER=user-id)
              ,NEW-CATID=cat-id2
              ,NEW-DIRECTORY-NAME=new.migrate.dir
//END

Now the original directory files for SYSBACKUP (backup.dir) and SYSMIGRATE (migrate.dir) must be deleted. The directory file new.backup.dir must be renamed to backup.dir, and new.migrate.dir to migrate.dir, since these names are used by the HSMS archives SYSBACKUP and SYSMIGRATE.

The user ID files must then be reconstructed under the new catalog ID:

/START-HSMS
//RESTORE-FILES FILE-NAMES=:cat-id2:$user-id.
               ,MIGRATED-FILES=*CATALOG-ONLY
               ,JV-NAMES=:cat-id2:$userid.
              [,ARCHIVE-NAME=*SYSBACKUP]
//END

Note

The localization information in the catalog entries of the migrated files corresponds to the information contained in the SYSMIGRATE directory file. The HSMS statement REPAIR-CATALOG-BY-RESTORE is therefore not necessary.