Completing the recovery procedure without using RECON data sets

When the IMS subsystem is restarted, you must check the status of each database and area, and take necessary actions to complete the recovery procedure.

Before you begin

Before starting the steps in this topic, you must restart the IMS subsystem by following the steps in Restarting the IMS subsystem without using RECON data sets.

About this task

The steps in this topic guide you through the process of recovering DEDBs when the RECON data set cannot be used.

The entire recovery procedure is explained in three separate topics. The steps in this topic describe the third task, from the completion of IMS cold start to the end of the recovery procedure.

The following diagram depicts the flow of the recovery procedure from the completion of the IMS cold start to the end of the recovery procedure.

Figure 1. Operation procedure for no DBRC mode (DBRC=N) (Task 3 of 3)
This figure depicts the operation procedure of IMS DEDB Fast Recovery for no DBRC mode (DBRC=N). It shows the last task, which is operation procedure from the IMS cold start to the recovery completion. For details of the procedure, see the description in this topic.

Procedure

  1. Determine if any databases or areas have the status code of STOPPED.

    See the status codes in the Database Status list and in the DEDB Area Status list. If a database or an area has this status code, issue the /STO DB LOCAL command, the /STO AREA LOCAL command, or both.

  2. Determine if any areas have the status code of IOERR, CREATE, or INT.STOP(ADS).
    See the status codes in the DEDB Area Status list. If any areas have one of these status codes, run the DEDB Area Data Set Create utility.
    Note: You can run the DEDB Area Data Set Create utility any time after IMS online processing starts.
  3. Run the Database Image Copy utility for all the databases.

    The recovered RECON data set does not contain all necessary information for the Database Recovery utility and, therefore, the Database Image Copy utility must be performed for all databases as soon as possible.