Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Reorganizing user or catalog IDs

&pagelevel(5)&pagelevel

Changing the user ID while retaining the catalog ID:

Three variants are distinguished here:

  1. Restore with renaming of the user ID from archives with unmodified directory
    This variant has the disadvantage that when restoring from backup archives you must work in a different way for save files: before changing the user ID with renaming and after changing it without renaming. Also, with SHOW-ARCHIVE the files saved before the change remain assigned to the old user ID.

  2. Setting up new archives with a new directory for the new ID and copying save files from the old archive (before the ID is changed) to a new archive with renaming of the user ID
    This variant is only permitted for the HSMS administrator. When save versions are copied using this procedure from backup incremental saves it must be ensured that the basic full backup is also copied in this way.

  3. In the unmodified backup archive, creating a current full backup after the change using backup with FROM-LATEST-OR-S0 renaming of the user ID
    This variant is also only permitted for the HSMS administrator.

General rule

Migrated files must be recalled to S0 before changing the user ID.

Changing the catalog ID (without modifying the pubset type)

Four variants are distinguished here:

  1. Restore with renaming of the catalog ID from archives with unmodified directory
    This variant has the disadvantage that when restoring from backup archives you must work in a different way for save files: before changing the catalog ID with renaming and after changing it without renaming. Also, with SHOW-ARCHIVE the files saved before the change remain assigned to the old catalog ID.

  2. Setting up new archives with a new directory for the new catalog ID and copying save files from the old archive (before the catalog ID is changed) to a new archive with renaming of the catalog ID
    This variant is only permitted for the HSMS administrator. When save versions are copied using this procedure from backup incremental saves it must be ensured that the basic full backup is also copied in this way.

  3. In the unmodified backup archive, creating a current full backup after the change using backup with FROM-LATEST-OR-S0 renaming of the catalog ID
    This variant is also only permitted for the HSMS administrator.

  4. Converting the directory of an archive to the new catalog ID with DIRCONV
    This variant is possible if the directory only contains entries with the old catalog ID (for SM pubset or for decentralized organization with SF pubsets).

The change from the old to the new catalog ID is possible without any problem for the save files on disk.

Procedure for migrated files

With variants 1 to 3 all migrated files must be recalled to S0 before the catalog ID is changed.

With variant 4 it is sufficient (in addition to the DIRCONV conversion to the new catalog ID for the migration directory) to restore only the catalog entry of the migrated files - not the files.