For copy jobs, if the original job failed in the COPY phase with the FULL YES and RESETMOD YES options specified for table spaces, BMC AMI Copy also does the following things:
- Puts a T entry in the ICTYPE column of SYSIBM.SYSCOPY to prohibit incremental copying until a full copy is successfully made.
For special case table spaces, BMC AMI Copy issues a Db2 -TERM UTILITY command.
WarningImportant
Specifying TERM/RESET will also terminate XBM caching for restartable Snapshot Copies.
Subject to the warnings that follow, you can also clean up the BMCUTIL and BMCSYNC tables with Catalog Manager. If you have installed Catalog Manager you can issue the BMCUTIL TERM command within that product. For more information, see BMC AMI Catalog Manager for Db2 documentation.
ErrorWarning
Be aware of the following situations:
- If BMC AMI Copy changed the space status, you must manually reset it with the Db2 -START command.
- If a copy job was terminated in the COPY phase and it was specified using FULL YES and RESETMOD YES for table spaces, page-modification indicators might be partially reset. The next copy must be specified using FULL YES before making any more incremental copies because an incremental copy could not identify all changed pages.
- To terminate and clean up following a failed Snapshot Copy (an XBM supported copy), run BMC AMI Copy with the TERM/RESET option (Restart parameter (restartParm)).
- If the space was in COPY-pending status, BMC AMI Copy might have reset the status, so make a copy before updates.
- XBM caching for restartable Snapshot Copies will not be terminated. You must terminate the caching through XBM. For restartable Snapshot Copies, you must be using XBM.
