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 R+/CHANGE ACCUM 13.1.

Ordering change accumulation file data

Ordering log record data written to a change accumulation file makes it easier for 

R+/CHANGE ACCUM

, and you, to predict what is stored in the file. The order in which the log record data is recorded in the change accumulation file allows optimization when 

BMC AMI Recover

 is recovering several objects and taking log record data from these objects.

Data extracted from log records is written to each change accumulation file in order by target table space, DSNUM, page number, and log point. Target table spaces are ordered by EBCDIC collating sequence with respect to database name and then table space name. For example, log record data for table space A.AB is written to the change accumulation file before log record data for table space AA.A.

Following the log record data for each table space, log record data for the associated indexes is written in an order that corresponds to the ordering of spaces on a wildcarded image copy for the BMC AMI Recover for Db2 product. This ensures optimal use of recovery resources when you use image copies and change accumulation files in a recovery.

 

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