Terminating a BMC AMI Copy job during execution

If immediate termination of BMC AMI Copy is required, cancel the job by using the MVS or TSO CANCEL command.

Then use one of the methods described in Cleaning-up-the-BMCUTIL-and-BMCSYNC-tables to reset the space status and clean up BMCUTIL and BMCSYNC.

Related topics

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

Utility-parameters-on-the-EXEC-statement

Alternatively if you installed Catalog Manager with BMC AMI Copy, you can terminate your BMC AMI Copy job by issuing the BMCUTIL command to display the status of BMC AMI Copy jobs. Then you can optionally terminate any one of the jobs listed. If you terminate a job with the BMCUTIL command, you might need to manually start the space in its original status. However, this method will cause BMC AMI Copy to abend with a user ABEND code 3500 at the next sync point. The BMCUTIL and BMCSYNC tables are cleaned up, but you must manually reset the space status using the Db2 -START command. XBM registration is not terminated. We do not recommend this method.

For information about terminating a failed BMC AMI Copy job, see Restarting-a-failed-BMC-AMI-Copy-job and Cleaning-up-the-BMCUTIL-and-BMCSYNC-tables.

Warning

If you terminate an BMC AMI Copy job through Catalog Manager, a copy using FULL YES and RESETMOD YES for table spaces will have page-modification indicators partially reset. You must specify the next copy using FULL YES, because an incremental copy could not identify all changed pages. If you terminate restartable Snapshot Copies through Catalog Manager, XBM caching will not be terminated. You must terminate the caching through XBM.

If a copy involving an Instant Snapshot fails and you terminate or reset the utility ID, BMC AMI Copy does not delete any Instant Snapshot copies made by the failing copy.

 

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