Restoring RECON data sets if both are unusable

It is unlikely that both RECON data sets would be unusable. However, if this situation occurs, you must back up, delete, and redefine your RECON data sets, make an image copy of all applicable DBDSs, and close any open, out-of-date OLDSs.

To restore and resynchronize the RECON data sets with the databases:

Procedure

  1. Stop all jobs that require access to the RECON data set.
  2. Optional: If you can access both RECON data sets, use the VSAM access method services REPRO command to back them up. This step is optional, but recommended.
  3. Use the VSAM access method services utility to delete and redefine your RECON data sets.
  4. Issue the access method services REPRO command to restore one of the RECON data sets.
  5. Issue the REPRO command to restore the other RECON data set from the first.
  6. Issue the DBRC LIST.RECON command or the DSPAPI FUNC=QUERY API request to list one of the RECON data sets. Based on the list, determine which DBDSs IMS updated since you made the backup in Step 2. If you cannot determine which DBDSs have been updated, assume that all have been updated.
  7. Issue the DBRC CHANGE.IC command (or the DSPAPI FUNC=COMMAND COMMAND=CHANGE.IC API request) with the INVALID keyword to mark all image copy records in error for all applicable DBDSs in Step 6.
  8. Make an image copy of all applicable DBDSs from Step 6.
  9. Issue the DBRC BACKUP.RECON command (or DSPAPI FUNC=COMMAND COMMAND=BACKUP.RECON API request) to make a backup copy of the RECON data sets.
  10. Close any open, out-of-date OLDSs using the NOTIFY.PRILOG command (or DSPAPI FUNC=COMMAND COMMAND=NOTIFY.PRILOG API request) to clean up the new RECON data set.

The RECON data sets are now restored and resynchronized with the databases.

Note: If DBRC does not manage a large number of databases, it might be easier to use the following procedure:
  1. Stop all jobs that require access to the RECON data set.
  2. Define new RECON data sets.
  3. Initialize these RECON data sets.
  4. Register the environment (always keep a backup copy of the most recently initialized, but not yet used, RECON data set available).
  5. Take image copies of all databases.