Skip to Content
Information

This site will undergo a brief period of maintenance on Friday, 18 December at 12:30 AM Central/12:00 PM IST. During a 30 minute window, site availability may be intermittent.

Information
Space announcement This space now contains the documentation for all the following components:
  • CHANGE ACCUMULATION PLUS
  • IMAGE COPY PLUS
  • RECOVERY MANAGER for IMS
  • RECOVERY PLUS for IMS
We are no longer updating the individual documentation spaces for these components. For the latest documentation, see BMC AMI Backup and Recovery for IMS 5.2.

How the Automatic Restart feature works

The Automatic Restart feature works through a checkpoint data set that tracks the status of the job step and its associated tasks.

When a utility job step starts, the utility reads the checkpoint data set (which is unique for each job step) to determine whether the job step completed successfully the last time that it was executed:

  • If the last execution completed successfully, the utility performs a 'cold start' of the job step--the utility performs all tasks, just as if the Automatic Restart feature was not active.
  • If the checkpoint data set is empty, the utility also performs a cold start.
  • If the checkpoint data set indicates that one or more of the image copy tasks did not complete successfully during the last execution, the utility performs a 'warm start' (restart) of the job step--the utility performs only the tasks that did not complete during the last execution.

Related topics

Using-the-Automatic-Restart-feature

During restart, the utility performs additional verification of the JCL and input control statements to ensure that the currently executing job step matches the previous execution that did not complete. For example, the job name, step name, procedure name (if any), and names of databases or areas to be processed must be identical between the previous and current executions. If they are not, the utility terminates the job step with an appropriate error message.

As each utility task completes, the utility updates the checkpoint data set to indicate completion; if a restart is needed, this task is not repeated. Before the utility updates the checkpoint data set, the output image copy is closed, cataloged, and deallocated (if it is not part of a stack), and DBRC is notified.

If a job step needs to be restarted, you can obtain a list of tasks to be performed by including the SCAN(Y) keyword on the GLBL control statement.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Backup and Recovery for IMS 5.1