Recovering DEDBs without using RECON data sets

To recover DEDBs, you must identify the state of the system and determine the options for running an IMS DEDB Fast Recovery job.

Before you begin

Before you start your recovery procedure, see Considerations for recovering IMS 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 first task, from the start of the recovery procedure to the successful completion of an IMS DEDB Fast Recovery job.

The following diagram depicts the flow of the recovery procedure from the start of the recovery until the successful completion of an IMS DEDB Fast Recovery job.

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

Procedure

  1. Determine whether the IMS subsystem can be started with the /NRE or the /ERE command.
    • If the /NRE or the /ERE command can be used to start the system, use either of the commands to restart the IMS subsystem. In this case, the IMS subsystem does not need further recovery operations and you can exit your recovery procedure.
    • If these commands are not available, continue with Step 2.
  2. Determine the last and the previous OLDS.

    Check the console log to determine the ddname of the OLDS that was in use when IMS failed and the ddname of the previous OLDS. If an emergency restart has already closed the OLDS that was in use at the time of failure, determine the ddname of the OLDS that IMS used last and the ddname of the previous OLDS.

    If the OLDS that was in use at the time of IMS failure or the previous OLDS contains a log record X'4301' (OLDS entry table log record), IMS DEDB Fast Recovery uses it to create an OLDS entry table (DSET) and determines the required OLDS. However, if a DSET is not created, if an SLDS is required, or if DBRC=N and AUTO=N are specified, you must specify the ddname and data set name of all OLDSs and SLDSs after IMS recovery start checkpoint (indicated by the message DFR3301I).

    If SLDSs are required and are not allocated dynamically, a DD statement must be specified for each SLDS on the job control statement of IMS DEDB Fast Recovery. The ddname must be eight characters. Data sets must not be concatenated on DD statements.

    To allocate SLDSs dynamically, provide the SLDS names in the DFRXDYN0 user exit routine. For more information about the DFRXDYN0 user exit routine, see DFRXDYN0 user exit.

  3. If you are using an XRF complex, ensure that I/O prevention is complete.

    If I/O prevention is not complete, either wait for the I/O prevention process to end or reset Central Electronic Complex (CEC).

  4. If you are using a two-phase commit process environment, prepare Resync control statements.

    For information about preparing Resync control statements, see Preparing and using Resync control statements.

  5. Run IMS DEDB Fast Recovery with the DBRC=N option.
    See JCL and control statements for JCL requirements for IMS DEDB Fast Recovery.
  6. Check the result of the job.

    If the job ends abnormally, or if you receive return code of 16, analyze and correct the errors, and repeat from Step 4.

What to do next

The next recovery task is restarting the IMS subsystem. See Restarting the IMS subsystem without using RECON data sets for instructions.