ERO Table

The ERO table performs three functions:
The ERO table performs three functions:
  1. Overrides the standard report retention specified in NGENT and NGEND.
  2. Assigns reports to a STORGRP so they are backed up with other reports in the same STORGRP.
  3. Specifies when reports are to be migrated to secondary storage (OPTICAL or CENTERA) and assigns a retention for report copies residing on those devices.
SYSOUTs are given expanded retention status with entries in what is referred to as the
expanded retention table,
or ERO table. Expanded retention table entries are defined to
using the SARPATAB DD statement in the
started task JCL, and in the SARDSK2B batch job for optical migration.
You can use wildcards in the expanded retention table statements, to identify all SYSOUT IDs that contain a particular character string. You can specify wildcards at any location in the SYSOUT ID. ABC* and AB*C*D are valid SYSOUT ID entries in the table.
The terms expanded retention and permanent status are synonymous.
The Expanded Retention Option (ERO) of
uses a table to provide additional retention capabilities for specific reports or groups of reports. The base
product only allows retention based on database generations. A report may be retained in the database for
generations (NGEND initialization parameter) and on a backup tape for
generations (NGENT initialization parameter). Without ERO, all reports will have the same retention. ERO provides additional retention options based on generations, days, and copies.
Retention Parameters
ERO retention is specified in either DAYS, COPIES, and/or GENS.
  • DAYS (RETPD) is based on the date the report was archived.
  • COPIES refers to the number of versions that you wish to keep.
  • GENS is based on the generation number when the report was created. This is the number that
    assigns to all reports archived between standard backup cycles. If you specify GENS=2 and you archived the report in GEN 100, it will be scratched after GEN 101 has completed its standard backup.
Control statements specify the retention parameters in a sequential file that is accessible by the backup task through the SARPATAB DD statement. The control statements specify the reports that will receive these retention options. The report name may be all 32 significant characters, or from 0 to 31 characters followed by the wildcard character, the asterisk (*). For example, if the payroll register should be kept on the database for 30 days and on tape for 3 years, add a control statement to the ERO table as follows:
If all other payroll reports need be kept for only one year, add the following control statement to the ERO table:
The backup cycle searches the ERO table from the top to the bottom using the report name as a search argument. The first entry that matches the most significant characters (and the wildcard character if present) is used to obtain the report's retention options.
Special considerations apply if this table is sorted, the '/PAY*' statement would appear in the file ahead of the '/PAYREG' statement, and the payroll register report would obtain the same retention options as the other payroll reports.
More importantly, if a '/* ALL …' default report retention statement was in the sorted file, it sorts as the first statement in the ERO table, and all reports would then obtain retention options from the first entry in the table.
To prevent this type of sequence error from occurring,
validates the order of the ERO table before every backup cycle. When you change the ERO table, we recommend you run the SARVERO utility to validate the ERO table and prevent problems during the next
backup cycle.
Expiration of Retention
ERO retention can use any combination of COPIES, RETPD, and GENS. When more than one retention parameter is specified,
will keep the report until all retention parameters have been satisfied. Thus, if you use COPIES=2 RETPD=5,
will not delete any copies unless they are at least 5 days old. In addition it will always keep the last 2 copies of a report, even if they are older than 5 days. This is referred as the TOTAL retention of a report.
If no ERO retention is specified (COPIES, RETPD, GENS), the INIT PARM PCOPIES is used as the default.
TOTAL retention and tape retention are nearly the same because the backup cycle copies a report to tape according to the interval settings.
You can use the SARBKTUX (user exit) to target specific reports that should
be backed up to tape.