Initialization Parameters › Expanded Retention Initialization Parameters › EROPRO

EROPRO

The EROPRO parameter directs the processing decisions made by the Expanded Retention Option as they pertain to SYSOUTs not currently under ERO control.

Note: This parameter does not dictate how ERO applies to or maintains retention parameters for SYSOUT already under ERO control.

• Changes to retention parameters that can affect a SYSOUT that is already under ERO control are reflected in all SYSOUTs regardless of the setting of the EROPRO parameter and regardless of when the SYSOUT was created.

  As an example, a change to the retention value in an ERO Table entry for a SYSOUT or group of SYSOUTs are to be retroactively applied to all SYSOUTs regardless of the setting of the EROPRO parameter.

• SYSOUTs that are not under the control of ERO are affected by the setting of the EROPRO parameter.

  As an example, if a catch-all entry is added to the ERO Table (/*....) and the EROPRO parameter is set to NEW, only SYSOUTs in the current generation are to have the new ERO retention applied to them. SYSOUTs created in previous generations are not affected.

  If the EROPRO parameter is set to YES (or ALL), and the catch-all entry is added to the ERO table, then ALL SYSOUTs receive ERO retention regardless of when they were created.

We recommend that EROPRO be set to YES and left that way unless a large percentage of the database is under standard retention; then we recommend a value of NEW.

If using the SARINIT ARCHCHG=yyyy parameter to establish a baseyear, EROPRO must be set to YES.

Reports under ERO control have a location of PERM, DSK, PTAP, PTMP, PDK2, and PRM2. Reports not under ERO control have a location of DISK, TAPE, and TEMP.

Syntax:

EROPRO=NEW|YES|ALL

The default is NEW.

Values are as follows:

NEW

Only SYSOUTs in the current generation are eligible to switch to ERO retention.

YES

ALL SYSOUTs are considered, and the parameter is not reset to NEW at the end of the backup cycle.

ALL

A one-time request to reconsider the entire database.

This is reset to NEW at the end of the backup cycle.