FDREPORT VTOC Examples

This section shows examples that read the VTOCs of selected volumes directly (DATATYPE=VTOC, which is the default). All examples in this section are found in the JCL library installed with FDR. The member names are EX5440x.

A sample of the generated report is shown after each example; because of space limitations, it may be condensed. In examples where sorting is required, SORTALLOC=YES has been specified to dynamically allocate required SORT files; in your installation you may have to provide SORT JCL.

Report on prefix example

Report on all data sets starting with the hi-level index “ABC” on any online volume. The default report (see  FDREPORT-REPORT-Statement) is printed. No sorting is done; a separate page is generated for data sets selected from each DASD volume. Messages about volumes for which no data sets are selected are suppressed. The report is printed on SYSPRINT.

The generated report looks like:

Report by data set name mask example

Report on all data sets residing on online volumes starting with “TSO” whose last qualifier is “LIST” or “OUTLIST” and that have not been referenced in two or more days. Only the data set name, volume, and date of last use is printed. The generated report is printed on ABRMAP. A standard summary is printed for each volume processed. The summary report is printed on ABRSUM.

The generated report looks like:

The summary looks like:

VSAM report example

Report on selected ICF VSAM clusters on all online volumes whose serial number starts with “CICS”. A variety of VSAM fields are reported (many others are available). ENABLE=AUTOSTACK allows FDREPORT to stack fields with like attributes in order to fit the fields within the page width of 80 characters. All selected clusters are combined into one report, sorted on cluster name and component name within cluster.

The generated report looks like:

Report on ABR backups example

Report on the current ABR backup for all data sets with the index of “PAYROLL”. The page width is expanded to 132 characters. Associated DSCB information is also requested. All online volumes beginning with certain prefixes are searched. The report is sorted by DSN. The summary shows all ABR backup volumes required to restore all of the payroll data sets, which might be useful as a tape pick list. The backup date is printed with a 2-digit year.

The generated report looks like:

The summary looks like:

Execute predefined report example

Execute a report that has been set up in advance. The name of this report is “VTOCREP1”, which is a member in the data set “USER.REPORT”. This member contains a TITLE, REPORT, and PRINT statements. The FDREPORT step includes an XSELECT statement to identify the data sets to be reported; in this example, all data sets starting with “USER” and a numeric digit are selected.

Predefined reports are useful for end-users who have little knowledge of FDREPORT. Report formats and controls can be predefined by others and executed by end-users. The FDRLIB members can also contain XSELECT statements so that they can be entirely self-contained.

If member “VTOCREP1” in data set “USER.REPORT” contains:

then those data sets are selected from the catalog, VTOC information extracted, and the report looks like:

Report on poorly blocked data sets example

Report on all data sets that are using less than 70% of the maximum track capacity for the device on which they reside. Generally, these are data sets with small blocksizes, or blocksizes over a half-track (which wastes the rest of the track). The tests on blocksize and size (in tracks) are to eliminate data sets for which no meaningful capacity calculation can be done.

The generated report looks like:

The final total for all volumes in the form:

Select by filter example

Select any online data set that contains a 3-character first-level qualifier that starts with the letter “T” and contains the character string “YM” anywhere within any qualifier other than the first. Only data sets between 100 and 200 tracks in size are included. The report is sorted by data set name within volume, and is in standard ABR VTOC format (see FDRABRP-VTOC-Report).

The generated report looks like:

Report on IAM files example

Select all online IAM data sets and print statistics about them.

IAM is a product from BMC that provides a high-performance data-compressed transparent alternative for many VSAM clusters. Contact BMC Support for more information.

The generated report looks like:

Report on special IAM files example

Select all enhanced or extended-format IAM data sets and all IAM Alternate Indexes (AIXs) on production volumes and print information about them.

Identify full partitioned data sets example

Locate all partitioned (PO) and partitioned extended (POE) data sets on TSO volumes and report those that have less than five percent free space in the data set or the directory.

The generated report looks like:

Report on all offline DASD example

Report on data sets in the VTOC of all offline DASD. The FASTPATH and OFFLINE options must be enabled. UCBSTATS=OFFLINE reports on only offline DASD (otherwise both offline and online DASD are included).

The generated report looks like:

Report on selected offline DASD example

Report on data sets in the VTOC of offline DASD in a range of device addresses. The FASTPATH and SELECTOFFLIN options must be enabled.

The generated report looks like:

Report same data two ways example

Report on data sets on a set of DASD volumes, once for all data sets sorted by name within volume, and once for only ICF VSAM sorted by cluster name for all volumes together, reporting different fields in each report. To reduce overhead by reading the VTOCs only once, RPTYPE=DATA is used to generate a file of FDREPORT internal records on SYSUT2, then that data is read twice to produce the two reports.

Report poorly organized VSAM clusters example

Report on all ICF VSAM clusters over three Megabytes in size with more than five CA splits or more than 20 CI splits, and all clusters with over 16 extents, since all these might be candidates for reorganization. Clusters with the highest CA splits are listed first.

The generated report looks like:

Report data sets likely to get Sx37 example

Identify data sets likely to get Sx37 (out of space) abends or the equivalent VSAM error. All data sets with less than 10% free space are reported if they have no secondary allocation, or if they have 13 or more extents (50 or more for VSAM).

The generated report looks like: