Expanded retention table entries are input to the
started task using the SARPATAB DD statement. Expanded retention table statements are written as follows:
Expanded retention table entries are input to the
started task using the SARPATAB DD statement. Expanded retention table statements are written as follows:
/sysout-id  parameter {value}
A sysout-id ID can contain alphanumeric and the following special characters:
  • Blank “ “
  • Less than sign “<”
  • Left parentheses “(“
  • Plus sign “+”
  • Bar “|”
  • Ampersand “&”
  • Right parentheses “)”
  • Semicolon “;”
  • Not Sign “¬”
  • Broken bar “¦”
  • Comma “,”
  • Greater than sign “>”
  • Question mark “?”
  • Colon “:”
  • Single quote “’”
  • Equal sign “=”
  • Double quote ‘"’
A Report ID cannot start with a Blank.
If the sysout-Id contains spaces, it must be enclosed in quotes (single or double). Any quotes in Report-id must be entered as a pair of quotes because a non-paired quote will end the ID. For example, if the value were JIM’S REPORT it must be entered as ‘JIM’’S REPORT’ or “JIM’S REPORT”.
Table Updates (PDS Member)
Maintaining the ERO table as a PDS member allows concurrent updates to take place while the SARSTC archival task is active. Because the ERO table is reprocessed during every standard backup cycle, any updates would automatically take effect for the next standard backup cycle following the update.
When Do the ERO Table Statements Take Effect?
The expanded retention table statements in the SARPATAB DD statement of the
started task JCL go into effect after a standard backup of the
database. Interim backups, specified via the NBACKUP initialization parameter, do not evaluate SYSOUTs for expanded retention.
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.
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'.
SARVERO - ERO Statement Validation Utility
SARVERO can be run as a batch program which will validate the ERO Table in the same manner as the Backup Cycle and produce the same error messages and return codes. It will also run a Standard Backup
--no tapes will be mounted and no reports will be deleted. Its purpose is to just give you an estimate of how many reports and tapes will be scratched and/or migrated on the next standard backup.
A return code of zero indicates that no errors are found. The program will terminate with a User Abend U'0001' and error messages in the Job Log if errors are found.
Successful completion of the table syntax-checking will result in the execution of the backup cycle simulation. To prevent the simulated backup, specify a parm of ",TABLE" after the database high level qualifier.
JCL Requirements
Sample JCL for this utility can be found in member HAEXERO in your CVDEJCL data set.
//STEP   EXEC PGM=SARVERO,PARM='.....db_hlq......[,TABLE]' //STEPLIB  DD DISP=SHR,DSN=.........CVDELOAD //SARBKLST DD SYSOUT=* //SARPATAB DD DISP=SHR,DSN=.........parm_library(..ero_table..)
A report will be written to the file specified by the SARBKLST DD Statement similar to Backup Cycle output in the Archival Task (SARSTC). The report will display all reports and/or resources which will be deleted from the database during the next full standard backup cycle if the specified ERO Table is implemented. It will also list any tapes which would be expired and uncataloged.
  • db_hlq
    High level qualifier of the database.
  • [,TABLE]
    An optional parameter to execute only syntax checking and not backup simulation. The default is to run both entry sequence checking and backup simulation. The simulation can run for 30 minutes or longer.
  • ero_table
    Member name of the ERO table to be validated.
  • Return Codes:
    • zero
      Normal termination, no errors.
    • U'0001'
      Errors found, see the accompanying messages.