Previous Topic: SARVERO - ERO Statement Validation UtilityNext Topic: Writing ERO Table Statements


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.

where:

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.

Note: For more information about the messages that can be generated, see the Message Guide.