Previous Topic: Use a Catch-all Entry to Determine Where Report Retention is ControlledNext Topic: Use PRETAIN=TABLE When Reports are Under ERO Retention


Use EROPRO=YES when reports are under ERO retention

The EROPRO parameter should be set to EROPRO=YES unless a large percentage of the database is not under ERO retention. This will efficiently handle new report entries in the ERO table by allowing existing copies of a report to be re-evaluated based on new entries in the ERO table.

Business Value:

The re-evaluation of existing report copies based on the new entries in the ERO table will prevent data loss when report retention is being increased from the standard NGEND/NGENT values.

Additional Considerations:

The default value for the EROPRO parameter is EROPRO=NEW because ERO retention is not activated in CA View by default and it is the most efficient option when reports in the database are under standard retention. However, if you plan to use ERO retention and define a catch-all entry in the ERO table, all reports will be put under ERO retention control and EROPRO=YES becomes the preferred setting.