Restarting a failed BMC AMI Copy job

You can restart an BMC AMI Copy utility that fails to complete successfully.

To restart, you must use:

  • The same version of BMC AMI Copy
  • The same BMC AMI Copy utility ID parameter

You must tell BMC AMI Copy whether you want to:

Warning

We recommend that you always take one of the actions listed above and described in the referenced sections after the failure of an BMC AMI Copy job—do not ignore the failure. If you take no action, subsequent executions of BMC AMI Copy might fail and the space might be in an inappropriate status.

Related topics

Building-and-running-BMC-AMI-Copy-jobs

Processing-multiple-tasks

Recommended-practices-for-making-incremental-image-copy-practices

Terminating-a-BMC-AMI-Copy-job-during-execution

Utility parameters on the EXEC statement

Output copy data sets

BMC AMI Copy provides execution parameters that function for either a new utility or a restart. We recommend that you select the parameter that specifies the type of restart that you expect to use most often and code that on all jobs. Then, in case a restart is needed, nothing needs to be changed and the job can merely be resubmitted.

Be aware of the following considerations:

  • If you want to restart an BMC AMI Copy job for some catalog and directory spaces in database DSNDB01 or DSNDB06, read Restarting-catalog-and-directory-copy-jobs before you restart the job.
  • On a restart, the last table space of the failing job might not have statistics updated depending upon the failure point. A restart of a GROUP YES RUNSTATS YES copy loses the statistics information from previous spaces.
  • When BMC AMI Copy is using the IBM Db2 COPY utility to make a copy (DB2CATALOG or SHRLEVEL CHANGE RESETMOD YES), if there is a failure in between the time the IBM Db2 COPY utility registers the copy in SYSCOPY and when BMC AMI Copy sets the phase to TERM, a restart will get the message BMC30141E noting that the image copy is already registered and fail.

If you dynamically allocate the copy data sets, simply submit the job again. The job will run according to the value of the restart parameter you originally coded in the EXEC statement of your JCL.

If you allocate the copy data sets in the JCL, the following additional considerations might require changes in the JCL:

  • Copy data set disposition
  • Keeping the MVS and Db2 catalogs synchronized
  • Minimizing the amount of repeat processing
  • Minimizing the amount of manual intervention
  • Any job restart package requirements (if you are using such a package)

This section contains the following topics:

 

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