Expanded Retention Option › ERO Table Statements › When Do the ERO Table Statements Take Effect?

When Do the ERO Table Statements Take Effect?

The expanded retention table statements in the SARPATAB DD statement of the CA View started task JCL go into effect after a standard backup of the CA View database. Interim backups, specified via the NBACKUP initialization parameter, do not evaluate SYSOUTs for expanded retention.

Important! Do not specify FREE=CLOSE in the SARPATAB DD statement because the ERO table would be freed during the first backup cycle, and subsequent backups would not access it.

When running SARINIT, always verify that the ERO parameters appear on the OPTIONS IN EFFECT listing.

Note: If PRETAIN=TABLE and no SARPATAB DD statement is provided in the archival task (SARSTC) job stream, message SARPAR10 WARNING - SARPATAB DD STATEMENT MISSING is displayed, and the backup cycle abends with U'1010'. If a SARPATAB DD statement is present but points to an empty file, message SARPAR09 WARNING - ERO TABLE EMPTY is displayed, and the backup cycle abends with U'1009'.