Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Copy for Db2 13.1.

Starting an BMC AMI Copy job

You start the 

BMC AMI Copy

 job by submitting it for execution.

This topic describes conditions for starting an BMC AMI Copy job. 

Copy jobs for read-write databases

If the copies that you are making are for one or more spaces or partitions in a read-write database. Perform the following tasks:

  • Ensure all target spaces have an acceptable initial status before you start an BMC AMI Copy job (refer to Initial-status-considerations-for-copy-jobs for more information).
  • When you are planning for a point-in-time recovery and are copying DSNDB06.SYSCOPY, be sure to copy DSNDB06.SYSCOPY after copying all of the spaces whose image copies are registered in it, otherwise the copy information in it will not be valid. The wildcard DB2CATALOG accomplishes this for you; see Example-6-Copying-the-Db2-catalog-and-directory for an example. 

Jobs that use the MODIFY command

For jobs that use the MODIFY command, ensure that all target spaces have an acceptable initial status before you start a modify job.

(Refer to Initial-status-considerations-for-copy-jobs for more information.)

Important

If your SYSIN includes commands to make copies in addition to the MODIFY command, see BMC-AMI-Copy-data-set-DD-statements.


Related topic

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


 

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