Expanded Retention Option › EROPRO and Retroactive Retention Processing › Expanded Retention Option - ERO

Expanded Retention Option - ERO

The second type of retention, Expanded Retention Option (ERO) is available as an optional feature.

The retention options are defined using the ERO table and the following SARINIT initialization parameters.

EROOPT, EROPRO, PRETAIN, POPT, PCOPIES

where

EROOPT=YES

Specifies whether the ERO option is being used.

EROPRO=NEW

• NEW—Indicates to CA View that only newly archived reports should be evaluated for Expanded Retention. Reports from older generations which are controlled by standard retention should not be considered.
• YES and ALL—Indicate that all reports controlled by standard retention, new or old, should be evaluated for Expanded Retention. If the name of the report matches an entry in the ERO table, the retention is switched to ERO control.

Note: We recommend that EROPRO be set to YES and left that way unless a large percentage of the database is under standard retention.

Important! The EROPRO parameter settings do not control when a report is removed from ERO control. Once a report has been defined to ERO, it will remain under ERO control until its total ERO retention has expired. If you change a report's retention in the ERO table, the next standard backup cycle will apply that retention to all past versions of that report – not just the new versions. If you remove a report entry from the ERO table, the system will search for a more generic match and use the retention specified in that entry. If a more generic match cannot be found, the system will default to using PCOPIES. The important thing to remember is that once a report is switched to ERO control; it stays under ERO control until its ERO retention has expired.

Notes:

• Since PCOPIES defaults to a very small value, report(s) may be deleted.
• When you run the SARTDR/TADD utility, reports which have been added back into the database because of some recovery issue fall under a different category and are not considered 'OLD'. They are marked as 'recently TADDed' and will be evaluated regardless of the setting of the EROPRO parameter.