FDREPORT JCL Requirements

The following Job Control statements are required to execute the FDR Generalized Report Facility.

STEPLIB or JOBLIB DD statement

If FDR is not in the system link list (LNKLST), specifies the program library where FDREPORT resides. The library must be APF authorized.

EXEC statement

Specifies the program name (PGM=FDREPORT) and region requirement (REGION=). Since the storage requirements of FDREPORT vary depending on the functions requested, we recommends that you specify REGION=0M so that the maximum region is available.

ABRCSV DD statement

Specifies the variable blocked data set that is used for output if RPTYPE=CSV is specified. The LRECL of this data set is determined by FDREPORT and is equal to the sum of the maximum output length of all fields, each separating comma (,), plus four for the Record Descriptor Word (RDW). BLKSIZE is always equal to half track blocking for the DASD device defined. If a tape device is assigned, a BLKSIZE of 27,998 is defaulted.

If the ddname ABRCSV or the ddname specified by the CSVDDNAME keyword is not present, FDREPORT attempts to assign the output to ABRMAP or the ddname specified by the RPTDDNAME keyword. If that ddname is not present, the appropriate messages are issued and the run continues as an audit pass.

Important

If executing more than one PRINT command with RPTYPE=CSV in the same FDREPORT run and you want the output combined in one extract file, then specify ENABLE=MODOUTPUT on the DEFAULT or PRINT commands, or supply an ABRCSV DD statement with DISP=MOD. Otherwise, the output from the later PRINT replaces the output from the earlier PRINT commands.

ABRMAP DD statement

Specifies the report data set. It is usually a SYSOUT data set but can be directed to tape or DASD. DCB characteristics are RECFM=FBA and LRECL of the value of the PAGEWIDTH= operand (see “PAGEWIDTH=” in FDREPORT TITLE Statement) unless you override it; the default block size is BLKSIZE=0 (calculated by OPEN). When ABRMAP is not found within the JCL stream, the reports are output to the SYSPRINT DD Statement. The PAGEWIDTH= operand is ignored if ABRMAP is not present.

ABRSUM DD statement

If specified, the summary reports are printed on this data set. Usually a SYSOUT data set. If summaries are to be printed and ABRSUM is not found in the JCL, summaries are printed on ABRMAP DD Statement or on SYSPRINT DD Statement (if ABRMAP is also absent).

ARCHIVE DD statement

Specifies the name of an ABR Archive Control File, if the DATATYPE=ARCHIVE option is used to process data from an Archive Control File. This is not required if the Archive Control File whose name is in the ARCDSN option of the FDR Global Options is to be read; FDREPORT dynamically allocates it under DD ARCHIVE#. You may also specify the ARCDSN= operand of FDREPORT to dynamically allocate any Archive Control File.

BCDS DD statement

(Optional) This must point to the DFSMShsm or DFHSM Backup Control Data Set (BCDS). If you provide the data set name of the HSM control file via the BCDSCLUSTER= operand, this DD statement is not necessary; FDREPORT dynamically allocates the required file. This DD statement cannot be used if the BCDS is a multi-cluster file; use the operand instead.

CA1XTR DD statement

Specifies a data set to be used to access an extract file of the CA 1 tape management system when DATATYPE of CA1DSN or CA1VOL is specified. The DD statement name may be changed by the CA1XDDNAME= operand of the DEFAULT command.

DIAGPCH DD statement

Specifies the output data set when ENABLE=PUNCHDIAGNOS is specified, for the storage of a job stream to correct VVDS errors. FDREPORT forces DCB characteristics of RECFM=FB,LRECL=80; any valid block size may be specified, but it defaults to 80. DIAGPCH is usually a DASD data set (sequential or a member of a PDS). After reviewing this job stream, you can submit it to correct the VVDS errors.

DISKxxxx DD statements

Optional and usually unnecessary. When the ENABLE=ONLINE operand is specified on PRINT, VOL=, or VOLG= operands are specified on statements preceding PRINT, the desired volumes are dynamically allocated and DISKxxxx DD statements are not required.

If used, DISKxxxx DD statements specify the DASD volumes to be processed by statements that do not specify ONLINE, VOL=, or VOLG=. The first four characters of the ddname must be “DISK”, and the remaining one to four characters may be any characters valid in a ddname (0-9, A-Z, $, #, @). The DD statement should look like:

//DISKxxxx DD UNIT=unit,VOL=SER=vol,DISP=OLD

FDRLIB DD statement

Specifies a data set to be read for extra FDREPORT control statements. This data set is used if FDREPORT encounters an EXECUTE or PUNCH control statement. This data set can be a sequential data set or a partitioned data set but must have characteristics RECFM=FB and LRECL=80. The purpose of this data set is to store canned report formats and punch masks for execution by any user. The DD statement name may be changed by the FDRLIB= operand of the DEFAULT, EXECUTE, or PUNCH command.

FROMDD DD statement

Required if the COPY statement is used to copy the FDREPORT option values set in a previous version of FDREPORT to the new version. Must point to the load library containing the F$REPOPT module containing the option values set in the previous version.

MCDS DD statement

(Optional) This must point to the DFSMShsm or DFHSM Migration Control Data Set (MCDS). If you provide the data set name of the HSM control file via the MCDSCLUSTER= operand, this DD statement is not necessary; FDREPORT dynamically allocates the required file. This DD statement cannot be used if the MCDS is a multi-cluster file; use the operand instead.

OCDS DD statement

(Optional) This must point to the DFSMShsm or DFHSM Offline Control Data Set (OCDS). If you provide the data set name of the HSM control file via the OCDSCLUSTER= operand, this DD statement is not necessary; FDREPORT dynamically allocates the required file. This DD statement cannot be used if the OCDS is a multi-cluster file; use the operand instead.

RMMXTR DD statement

Specifies a data set to be used to access an extract file of the DFSMSrmm tape management system when DATATYPE of RMMDSN or RMMVOL is specified. The DD statement name may be changed by the RMMXDDNAME= operand of the DEFAULT command.

SORTxxxx DD statements

(Optional) If you include the SORT or generate a report with data from multiple DASD volumes, you may need to specify DD statements (for example SORTLIB, SORTWKnn) required by your system SORT product.

However, any or all of these SORT DD statements may be omitted if you have requested dynamic allocation of the SORT data sets via the SORTALLOC= operand of PRINT.

SYSIN DD statement

Specifies the control statement data set. Usually a DD * or input data set.

SYSLIB DD statement

Required if either:

The CHANGE=PERM or CHANGE=RESET options are specified on a DEFAULT statement, in order to permanently change FDREPORT default processing options.
The COPY statement is used to copy the FDREPORT option values set in a previous version of FDREPORT to the new version.

Must point to the load library containing FDREPORT and you must have UPDATE authority to that library.

SYSPRINT DD statement

Specifies the primary output message data set; it is required. It is usually a SYSOUT data set. DCB characteristics are RECFM=FBA and LRECL=121; the block size defaults to 1210 on DASD or tape.

SYSPUNCH DD statement

Specifies the output data set when RPTYPE=SELPCH is specified, for the storage of generated statements. FDREPORT forces DCB characteristics of RECFM=FB and LRECL=80; any valid block size may be specified, but it defaults to 80.

SYSPUNCH may be a DASD data set (sequential or a member of a PDS), but it may also be assigned to the JES internal reader SYSOUT=(class,INTRDR) to submit a complete job stream for execution. You may also make SYSPUNCH a normal SYSOUT data set if you wish to view the generated statements.

SYSUDUMP DD statement

Recommended in all FDREPORT jobs in order to more easily diagnose error conditions that make FDREPORT abend. Usually a SYSOUT data set. If you have a debugging aid product on your system that would prevent the desired dump, please add the appropriate one of these statements to the JCL so that a fully-formatted dump is produced.

//ABNLDUMP DD DUMMY     Print normal IBM dump in addition to the Abend-AID Report 
//CAOESTOP DD DUMMY     Turn off CA OPT II & CA SYMDUMP 
//DMBENAN  DD DUMMY     Turn off DumpMaster 
//ESPYIBM  DD DUMMY     Turn off Eye-Spy 
//IDIOFF   DD DUMMY     Turn off IBM Fault Analyzer

SYSUT1 DD statement

Required when the RPTYPE=DATA (or COMPDATA) and DATATYPE=EXTRACT operands are both specified on the same PRINT statement. Although SYSUT2 would normally be used for the data input, it cannot be used as both input and output in the same operation; in this case, SYSUT1 is used instead of SYSUT2 for the extracted data input, and SYSUT2 is used for output. The SYSUT1 DD statement name may be changed by the ALTDATADDNAME= operand.

SYSUT2 DD statement

Required when the RPTYPE=DATA (or COMPDATA) or DATATYPE=EXTRACT operands are specified, for the storage of FDREPORT internal data records. Normally a DASD data set but it may be on tape. If you want to use this extract file as input to another reporting program (such as SAS), the format of the records is defined by the @RPTDS macro that is a member in the FDR Installation FDRSAMP.

When RPTYPE=DATA or RPTYPE=COMPDATA is specified it is an output data set and FDREPORT forces DCB characteristics of RECFM=VB,LRECL=8200; any valid block size can be specified, or FDREPORT assigns a default value.

If you execute several PRINT statements in the same FDREPORT step, each with RPTYPE=DATA (or COMPDATA), and you want the extracted data from each to accumulate in the SYSUT2 data set, you must either specify DISP=MOD in the JCL or the ENABLE=MODOUTPUT operand. Otherwise, only data from the last PRINT is available.

For DATATYPE=EXTRACT, SYSUT2 is used as input; it must be a data file created by the RPTYPE=DATA option of FDREPORT in an earlier step or job or earlier in this step. Although the format of the extract file has changed in various releases of ABR, FDREPORT can successfully process any extract file created by any prior release. You can concatenate several extract files as one input if they were created with RPTYPE=DATA; extract files created with RPTYPE=COMPDATA cannot be concatenated.

If required and not present in the JCL, FDREPORT allocates an extract data set. If the EXTRACTDSN= operand is specified, the existing data set named is allocated; you may optionally include the EXTRACTMEMBER= operand to select a member of a PDS for input or output. If EXTRACTDSN= is not included, a temporary data set is allocated, which is retained for the duration of the step so that it can be used as output and later as input when DATATYPE=EXTRACT is specified on another PRINT statement.

The SYSUT2 DD statement name may be changed by the DATADDNAME= operand.

TAPExxxx DD statements

Required only if DATATYPE=TVTOC is specified. These DD statements must point to FDR-format backups on tape or DASD; all backups created by FDR, FDRDSF, FDRABR, and SAR can be used. All of the TAPExxxx DD statements in the step are read when DATATYPE=TVTOC is used.

TMC DD statement

(Optional) This must point to the CA 1 Tape Management Catalog (TMC). If you provide the data set name of the TMC via the CA1TMC= operand, this DD statement is not necessary; FDREPORT dynamically allocates the required file.

FDREPORT under TSO

FDREPORT may also be executed under TSO. Any required files must be preallocated (corresponding to the DD statements above). If the library containing ABR is in the link list (LNKLST), then wherever you can enter a TSO command, you can simply type:

FDREPORT

If not, then you can type:

CALL 'fdrlib(FDREPORT)’

In either case, FDREPORT prompts for statement input. Enter “END” to terminate FDREPORT. The SYSIN and SYSPRINT file names should be allocated to your terminal before invoking FDREPORT.

If you have the ABR ISPF panels installed, option A.1 (REPORTS) gives you the ability to generate predetermined reports with FDREPORT (using the EXECUTE statement to select the report format from a library, with a XSELECT statement generated from the panel.

However, ISPF option A.S (the SRS dialog, described in FDRSRS - Search, Report, and Services Dialog) internally uses FDREPORT to generate much of its data, giving you the ability to interactively do the same selection and reporting as done by FDREPORT.