Restarting failed recovery jobs

To restart a single failed recovery job

1. Make a backup copy of the recovery JCL before you begin to edit it for restart.
2. Add a RESTART= stepName option to the BMC AMI Recovery Manager job statement, where stepName is the name of the job step that failed during the prior execution.
3. Continue as follows:

   1. If the failed job step is a DSNUTILB step,

      • Issue a Db2 -DISPLAY UTILITY(*) command to determine whether Db2 considers it necessary to restart the utility.
      • If the recover utility appeared in the previous DISPLAY UTILITY(*), add RESTART as the third parameter on the recovery job step EXEC statement.

      For example, if the subsystem ID is DBDF, the parameter list should look like the following:

      EXEC PGM=DSNUTILB,PARM='DBDF,,RESTART'
   2. If the failed job step is a BMC utility, no modification to the restart parameter is necessary. BMC AMI Recovery Manager uses NEW/RESTART for BMC AMI Copy, NEW/RESTART(PHASE) for BMC AMI Recover, and NEW for CHECK PLUS.

   3. If the failed job step is the execution of the ARMBSTP program preceding the IDCAMS DELETE step required to support the Delete STOGROUP objects and Redefine VCAT object options, do one of the following:

      • Wait for the objects to stop and restart the job at the next step.

      • Submit the job again.

        If you want to change the number of times that ARMBSTP attempts to stop the objects or the wait period between attempts, you must change the values in the ARMBSTP job step. The default values are 30 tries and 2 second wait time.

      No other modifications are necessary to restart BMC AMI Copy and CHECK PLUS. However, restarting BMC AMI Recover and DSNUTILB may require modifications to DD statements in those job steps.

      Important

      BMC AMI Recovery Manager uses the default utility ID for each Db2 utility and each BMC utility.

      For more information about restarting an IBM or BMC utility, refer to IBM reference manual.

4. Submit the edited JCL.