Updating recovered control data sets using UPDATEC

For performance reasons, you should use the enhanced CDS recovery function instead of the UPDATEC command to recover your control data sets. If you do use UPDATEC, the forms of the command are:

  UPDATEC BACKUPCONTROLDATASET

  UPDATEC BACKUPCONTROLDATASET JOURNAL(dsname)

  UPDATEC MIGRATIONCONTROLDATASET

  UPDATEC MIGRATIONCONTROLDATASET JOURNAL(dsname)

  UPDATEC OFFLINECONTROLDATASET

  UPDATEC OFFLINECONTROLDATASET JOURNAL(dsname)

  UPDATEC ALL

  UPDATEC ALL JOURNAL(dsname)

The forms with no journal specified use the current (active) journal data set to update the specified data set. The forms with a journal specified use a backed up journal data set requested by dsname to update the specified data set. For example, the command UPDATEC BACKUPCONTROLDATASET applies the transactions recorded in the active journal data set to the backup control data set. Thus, if the backup control data set were a copy of the last backup version of the backup control data set, the UPDATEC command would modify it to the state of the backup control data set before it was lost or damaged.

If the most-recent backup version of a control data set is also damaged, you can still recover the control data set by a three-step process:

Import the next-most-recent backup version of the data set.
Run UPDATEC with the journal that corresponds to the next-most-recent backup version. This journal is the most-recent backed up journal.
Run UPDATEC with the current journal.

Note: The UPDATEC command may be used to recover a damaged control data set. However, UPDATEC can take a long time to run. Because the process holds an exclusive enqueue and reserve on all the control data sets, no other DFSMShsm functions (such as RECALL) can be run when UPDATEC is running. Therefore, a complex will not be able to do any DFSMShsm work until UPDATEC finishes. In a JES3 environment, the whole complex may be unavailable until UPDATEC finishes processing.