Your Product Installation and Configuration Best Practices › Configuration › Use a Catch-all Entry to Determine Where Report Retention is Controlled

Use a Catch-all Entry to Determine Where Report Retention is Controlled

Use a catch-all entry as the last entry in the ERO table to make it easier to determine where report retention is controlled. This will enable all reports in the CA View database to be under ERO retention, and you will only have to look in one place to determine report retention specifications.

Business Value:

The catch-all entry is a simple technique to define safe retention criteria to all reports in the database as a safety net, and it significantly reduces the risk of data loss due to human error.

Additional Considerations:

The following SARINIT parameters and ERO table entries can be used as an example for describing the benefits of a catchall entry:

NGENT=60
NGEND=3
EROOPT=YES
EROPRO=NEW
PRETAIN=TABLE

Include the following entry at the end of the ERO table:

/*     ALL GENS=60 DGENS=3

Note: GENS=NGENT and DGENS=NGEND.

Since the ERO table is searched in entry sequence, this catchall table entry will match reports that have not been defined by any previous entry. Therefore, every report in the whole database will be under ERO retention and you will only have to look in one place to determine report retention.