Terminating the utility (no plans to restart the job)

If you intend to terminate a utility after it fails and have no plans to run another BMC AMI Copy utility, you must satisfy both of the following requirements.

Important

If you are making image copies, these apply regardless of how you allocate the copy data sets.

Related topic

Restarting-a-failed-BMC-AMI-Copy-job

  • Do not specify a restart parameter value in the original job or job step.
  • Specify TERM/RESET as the value of the restart parameter in the BMC AMI Copy JCL and submit the terminating utility for execution again.

This method is not recommended for normal operation. However, if for some reason you do not plan to restart a failed utility, you should use the TERM/RESET restart parameter to run BMC AMI Copy. This cleans up the BMCUTIL and BMCSYNC tables and any related XBM processing and resets the space status if BMC AMI Copy changed it. If you neglect to clean up the BMCUTIL and BMCSYNC tables in this way, subsequent executions of BMC utilities might fail. Also, failure to reset the space status in this way might leave the space in an inappropriate status, such as RO, STOP, or COPY.

For table spaces, when you use TERM/RESET to restart a job that failed in the COPY phase and the original job used the FULL YES and RESETMOD YES options, BMC AMI Copy puts a T entry in the ICTYPE column of SYSIBM.SYSCOPY to prohibit the making of an incremental copy until a full copy is made. If a table space was in COPY-pending status, BMC AMI Copy might have turned off the flag so a copy must be made before updates.

 

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