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.

Bypassing spaces with a bad status

With the COPY, QUIESCE, RECALL, and MODIFY commands, you can use ON ERROR BADSTATUS to tell 

BMC AMI Copy

 what action to take if a space or partition is in an unacceptable status, or has a BMC or Db2 utility running against it.

Use ON ERROR BADSTATUS SKIP to bypass the space or partition, issue a message, and continue processing. Use ON ERROR BADSTATUS END to tell BMC AMI Copy to terminate processing with a RC=12.

If a space is skipped because of ON ERROR BADSTATUS SKIP, the space will not be retried if the job abends and you retry the job with a NEW/RESTART. Here is an example:

COPY TABLESPACE a.a, a.b, a.c
ON ERROR BADSTATUS SKIP

If table space a.b is skipped because of a status problem and the copy abends in the COPY phase while copying table space a.c, when the copy is restarted, BMC AMI Copy ignores table space a.b and restarts table space a.c in the COPY phase.

Related topic

Concurrency-issues

 

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