ARMBLGR—Log range analysis

The ARMBLGR program performs log range analysis for a subsystem and captures information for each part of every table space and every index in the subsystem.

This information is saved in the BMC AMI Recovery Manager log range file (the ARMLRNG file).

The analysis is required by ARMBGEN when performing a local point-in-time recovery using a conditional restart. You can dramatically improve processing time by avoiding the unnecessary recovery of objects that have not changed between the current time and the recovery point. Use the ARMBLGR program to perform batch log range analysis prior to a local point in time (PIT) recovery of the full subsystem in order to identify objects that have not changed. Be aware that unchanged processing does not occur for indexes unless they have the COPY YES attribute.

Related topics

Generating-JCL-for-local-recovery

BMC-AMI-Recovery-Manager-batch-programs

BMC-AMI-Recovery-Manager-subsystem-recovery-programs


Important

ARMBLGR writes its analysis to the BMC AMI Recovery Manager log range file (the ARMLRNG file). Each subsystem and data sharing object set has a defined log range file that is tracked by the .LRNG option in the BMC AMI Recovery Manager option set. (Data sharing members share the same log range file.)

The log range file is defined during product install. If for any reason, you need to redefine the file, allocate a 50-cylinder file as FB, LRECL 392.

You can create the ARMBLGR JCL in the following ways:

  • Manually code JCL to run ARMBLGR. This method completely avoids using a TSO session.
  • Use online support that is provided by BMC AMI Recovery Manager to create ARMBLGR JCL. For more information, see Generating-JCL-for-local-recovery.

This section contains the following topics:

 

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