Migrating Catalogs

Catalog Migration Using BACKUP/RESTORE

You cannot actually back up and restore catalogs under BACKUP/RESTORE, but when you back up and restore objects (including empty objects), their catalog information is backed up and restored too. This makes it possible for you to use BACKUP and RESTORE to copy objects and their catalog information into a different catalog. If the new catalog already contains an entry name for the object restored, the original object is deleted, and the restored object is added to the new catalog.

Catalog Migration Using DEFINE/REPRO/ALTER

Although you cannot copy a user catalog itself the following procedure can be used to migrate (move to another volume) a user catalog and the required files using DEFINE/REPRO/ALTER commands.
  1. Define the new user catalog (procedure described above) on a new volume using a temporary catalog name that is not already in the system.
  2. Define any VSE/VSAM data spaces required for the new volumes. Note that the define catalog operation has already defined a data space on the catalog volume. Any space to be occupied by unique files should be left unallocated.
  3. Define all the files, alternate indexes and paths using the old names from the source catalog.
  4. REPRO every file and its alternate index onto the new volume.
  5. Delete and disconnect the source catalog entry from the system.
  6. Change a temporary catalog name of the new catalog to the source catalog name using ALTER NEWNAME USERCATALOG.

Although this method might be slower than Backup/Restore, it allows to move the user catalog and files to the new device type as well as perform the data reorganization during the move.

Catalog Migration Using EXPORT/IMPORT

Moving a Master Catalog to Another Volume:

  1. Using EXPORT, create portable copies of all files that are to be in the new catalog (procedure described below). For EXPORT, DISCONNECT any user catalogs to be reconnected to the new catalog.
  2. IPL with the master catalog assigned to the new volume, using the IPL DEF SYSCAT=cuu command.
  3. Define the new master catalog (procedure described above).
  4. Define any VSE/VSAM data spaces required for the volumes. (You need not delete files and catalogs belonging to another catalog.) Note that the define catalog operation has already defined a data space on the catalog volume. Any space to be occupied by unique files should be left unallocated.
  5. Using IMPORT, copy VSE/VSAM files to volumes belonging to the new catalog. (For considerations on moving to a different device type, refer to Migrating VSE/VSAM Files to Another Device.) If IMPORT was used, you can IMPORT CONNECT user catalogs.

Moving a User Catalog to Another Volume:

  1. Using EXPORT, create portable copies of all files that are to be in the new catalog (procedure described below).
  2. Delete or disconnect the previous user catalog entry unless it is owned by a different master catalog.
  3. Define the new user catalog (procedure described above).
  4. Define any VSE/VSAM data spaces required for the volumes. (You need not delete files and catalogs belonging to another catalog.) Note that the define catalog operation has already defined a data space on the catalog volume. Any space to be occupied by unique files should be left unallocated.
  5. Using IMPORT, copy VSE/VSAM files to volumes belonging to the new catalog. (For considerations on moving to a different device type, refer to Migrating VSE/VSAM Files to Another Device.)