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 Recovery Manager for Db2 13.1.

Troubleshooting an ARMBSRR job

When you execute the ARMBSRR job, you might receive error or warning messages.

You should always correct any error situations, and then rerun the job before transporting the system resource recovery job to the recovery site.

In general, you should take the following return code-dependent actions:

  • If you receive a return code 4, good JCL has been generated but you should examine the warning messages and take appropriate action.
  • If you receive a return code 8, JCL is generated but some values are missing. The JCL will not run until you correct the problems.

  • If you receive a return code 12, no JCL has been generated. The errors must be corrected before you run the ARMBSRR job again.

    For more information, see Running-and-restarting-Db2-conditional-restart-recovery-jobs.

    The following messages are the most important ARMBSRR messages. Full explanations and user actions are provided in BMC-AMI-Recovery-Manager-Repository.

    Message Number

    Short explanation

    BMC80300E

    Db2 was not active when ARMBSRR executed.

    BMC80403W

    No JCL was generated for a specified operation.

    BMC80424W

    BMC AMI Recovery Manager could not find the required integrated catalog facility (ICF) data.

    BMC80607E or W

    BMC AMI Recovery Manager found an uncataloged archive log copy.

    BMC80608E or W

    BMC AMI Recovery Manager could not find a specified archive log copy.

    BMC80609I

    BMC AMI Recovery Manager increased the active log allocation.

    BMC80614E

    An archive-history-file read error occurred.

    BMC80615E

    BMC AMI Recovery Manager could not find an archive log with a specified start RBA.

    BMC80618E

    The OFFSITE NO option can be used only in dual logging environments.

    BMC80620E

    OFFSITE NO ARCHIVE1 is invalid when the recovery site archives will not be cataloged.

    BMC80621W

    No stacked tape analysis will occur due to previous errors.

    BMC80622W

    No copies were found for the indicated table space, so no stacked tape analysis will occur.

Related topics

ARMBSRR—System resource recovery

ARMBSRR-jobs


 

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