Reporting RUV data in batch
RUV produces a variety of batch reports that show repository contents. These contents include VSAM data sets selected for recovery, APPLID and FILEID data, archived data sets, backup file data sets, log of log data, system variables and user variables, and rule set information.
You should use reports to display various types of data created in your environment including the current state of the data. First use the following RUVZSM0 batch interface JCL. Then use the REPORT command to display repository data (for further JCL setup explanation, see Using RUV interfaces).
//*STEPLIB DD ==>IF REQUIRED
//SYSPRINT DD SYSOUT=*
//SYSINDD *
Most RUV reports accept lists of values as parameters. These values may contain wildcard characters. Parameters allow you to restrict the data to the information you need to see. Use the following command to set a wildcard search for all instances of a specified report type:
Many of the RUV reports also accept filter keywords. Filter keywords allow you to further restrict the selection of data that you are interested in. The keywords START_TIME, STOP_TIME,and LOCATION are accepted as filters for reporting archive and backup file data as shown in the following example:
REPORT report_type(*)
START_TIME(start_time)
STOP_TIME(stop_time)
LOCATION(location);
The REPORT command can be especially useful before you delete information from the repository (recommended). Use the REPORT command as previously shown to examine data before deletion from the repository. When you are satisfied with what will be deleted, change the REPORT keyword to the DELETE keyword. Rerun the job to delete the previously reported information as shown in the following example:
DELETE report_type(*)
FILTER_BY(
START_TIME(start_time)
STOP_TIME(stop_time)
LOCATION(location);
This section contains the following topics:
Related topic