Retention Processing

CA View uses two types of report retention - standard and ERO.
CA View uses two types of report retention - standard and ERO.
  • The first type (which is part of the base product) retains reports based on database 
    . This is known as standard retention. You can easily identify reports that are controlled by standard retention. The online report selection list will show one of the following locations - DISK, TAPE, or TEMP.
  • The second type, Expanded Retention Option (ERO), retains reports using database initialization parameters and an ERO Table.
When a report is originally archived; it is always controlled by standard retention. During a standard backup cycle, the EROPRO parameter controls which reports are eligible to switch from standard to ERO retention.
Retention Based on Generations - Standard Retention
A database generation is equivalent to all reports that have been archived between STANDARD backup cycles. Even if a report is created multiple times before or during a standard backup cycle, all copies are in the same generation. This means that every time a standard backup cycle is executed, the database generation is incremented. If three standard backup cycles are run each day then a day is equal to three database generations.
If a report's retention is not controlled by the ERO table, then it defaults to retention controlled by the NGEND/NGENT SARINIT parameters.
NGEND indicates how many generations a report should be retained on disk. For example, if NGEND=1 and we are currently archiving generation 10, all NON-ERO reports from generation 10 and prior will be removed from disk during the next STANDARD backup because this is the start of generation 11.
NGENT indicates how many generations the report should be retained in the system, that is, on tape. Since a report will be written to tape during the first backup cycle after it is archived, it is available in two locations, disk and tape so the value includes NGEND, that is, if NGEND=10 and NGENT=30, the report will remain on disk for 10 generations and a total of 30 generations.
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.
Specifies whether the ERO option is being used.
  • 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.
We recommend that EROPRO be set to YES and left that way unless a large percentage of the database is under standard retention.
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.
  • 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.
The PRETAIN Parameter and ERO Retention
The PRETAIN parameter controls what happens to a report after its total ERO retention has expired. It controls whether a report should switch back to standard retention or should it be deleted.
  • INIT
    indicates that the report is to switch back to standard retention unless the ERO table entry for this report contains the DELETE parameter. When the DELETE parameter is not specified, the report is kept until it exceeds the NGENT/NGEND specification, then it is deleted
    Indicates that the report is to be deleted.
    We recommend setting PRETAIN=TABLE