Executing Log Analyzer for Db2 for z/OS (PLA) batch DDL and DML reports which fails with:
LAE0288I Beginning Image Copy merge processing.
LAE0181I AN RBA RANGE THAT IS BEFORE ANY ARCHIVE LOG
LAE0181I DATASET RANGES HAS BEEN REQUESTED.
LAE0181I THIS RANGE MAY HAVE ROLLED OFF THE BSDS
LAE0031E - Image copy merge task error
Enable DATA CAPTURE CHANGES as documented in the PLA User Guide;
Use of DATA CAPTURE CHANGES
Each table has a data capture attribute that can be set to DATA CAPTURE CHANGES (DCC) or DATA CAPTURE NONE (DCN). The data capture attribute
dictates how much data is logged for an update transaction to that table. When DATA CAPTURE NONE (DCN) is used, the log record contains only the
changed data. When DATA CAPTURE CHANGES (DCC) is used, the log record contains enough information to build a full before and after-image of
the changed rows. This parameter is specified in the CREATE TABLE or ALTER TABLE SQL statement for the table.
Although PLA attempts to construct complete SQL statements, its ability to do so depends upon the amount of detail in the DB2 log files. Best results
are achieved by enabling DATA CAPTURE CHANGES. This consideration is important if you are generating SQL using the detail (D) option,
because this option uses only the information that is presenting the logs.
If you retain current image copies and the necessary archive logs, you can avoid use of DATA CAPTURE CHANGES.
Also refer to the Log Analyzer Additional Processing Steps within the Installation Documentation under section titled How to Upgrade to
New DB2 Versions or Modes for DATA CAPTURE CHANGES recommendation for SYSIBM DB2 catalog tables.