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.

Optimized recovery JCL

BMC AMI Recovery Manager

 optimizes the performance of your JCL based on the recover utility you select and the maximum number of jobs you use.

For the best results, you should:

  • Select BMC AMI Recover as the recover utility
  • Provide a number for the maximum number of jobs that you want to use (based on your processing environment)

  • BMC AMI Recovery Manager creates multiple recovery jobs that run concurrently whenever possible.

    For more information, see Multiple-job-optimization for more information.

    Important

    For some scenarios, you can choose to generate the multiple recovery jobs into separate members to provide more control over job submission. For more information, see Separating jobs from a multi-job batch job stream.

  • BMC AMI Recovery Manager streamlines tape unit use by analyzing stacked input image copies and generating the DD statements.
  • BMC AMI Recovery Manager specifies REGION=0M for BMC AMI Recover job steps. If you code a value for REGION in your job card, that value will override the BMC AMI Recovery Manager specification on all job steps.

  • When you are recovering indexes, using a check utility, or making output copies after a recovery, BMC AMI Recovery Manager automatically sizes the data sets, based on the data set sizing value that is set in the utility options. Data sets in groups that are created by using the ARMBGPS do not require automatic sizing based on the data set sizing value.

    Tip

    To enable BMC AMI Recovery Manager to provide highly accurate estimates of data set sizes and minimize the time that is required to provide those estimates, use the RUNSTATS utility regularly to record up-to-date statistics in the Db2 catalog.

  • BMC AMI Recovery Manager groups indexes to minimize table space scanning. It also groups spaces to minimize log scanning when applying log records to the spaces that are being recovered.
  • If symbolic names are specified for output image copies, BMC AMI Recovery Manager expands them and passes the results to BMC AMI Recover or IBM Db2 COPY when those utilities are utilized. If BMC AMI Copy is the utility of choice, the symbolic names are passed to BMC AMI Copy.
  • If you use a check utility, the work space that is required is limited by using one job step per object. The amount of work space is limited in the same way when indexes are recovered by IBM Db2 RECOVER.

Related topic

Recovering object sets

 

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