Creating your own batch reanalysis job

Batch mode can also be invoked via JCL that you have created or saved from a job previously generated by Fault Analyzer and later modified if necessary. If you are performing reanalysis of a fault entry, specify the FaultID option. If you are performing analysis of an MVS dump data set, specify the DumpDSN option.

JCL can be generated using the B line command from the Fault Entry List display. This is the preferred method of performing batch reanalysis, because it will automatically add JCL DD statements for side file data sets and any STEPLIB concatenation that was in effect during real-time processing.

Your job might, for example, look like this:
Figure 1. Sample batch reanalysis job
//RTURNERA JOB (),'FAULT ANALYZER',CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID
//*
//* Allocate a PDSE for compiler listings
//*
//ALLOC    EXEC PGM=IEFBR14
//DD1      DD  DISP=(,CATLG),DSN=&SYSUID..COBLIST,SPACE=(CYL,(1,1,5)),
//             DCB=(RECFM=FBA,LRECL=133),DSNTYPE=LIBRARY
//*
//* Recompile MYPGMA
//*
//CBLCOMP  EXEC IGYWC,PARM.COBOL='LIST,MAP,Source,XREF'
//COBOL.SYSIN  DD DISP=SHR,DSN=MY.COBOL.Source(MYPGMA)
//COBOL.SYSPRINT DD DISP=SHR,DSN=&SYSUID..COBLIST(MYPGMA)
//*
//* Recompile MYPGMB
//*
//CBLCOMP  EXEC IGYWC,PARM.COBOL='LIST,MAP,Source,XREF'
//COBOL.SYSIN  DD DISP=SHR,DSN=MY.COBOL.Source(MYPGMB)
//COBOL.SYSPRINT DD DISP=SHR,DSN=&SYSUID..COBLIST(MYPGMB)
//*
//* Reanalyze SYSMDUMP data set
//*
//RUNDA    EXEC PGM=IDIDA,PARM=('/DumpDSN(MY.DUMPDS)')
//SYSPRINT DD  SYSOUT=*
//IDILCOB  DD  DISP=SHR,DSN=&SYSUID..COBLIST
//*
//* Delete temporary compiler listings PDSE
//*
//DELETE   EXEC PGM=IEFBR14
//DD1      DD  DISP=(OLD,DELETE),DSN=&SYSUID..COBLIST

The job includes the recompilation of two COBOL programs, MYPGMA and MYPGMB. These are assumed involved in the fault being reanalyzed, but their compiler listings might not have been available to Fault Analyzer during real-time analysis. Providing them to the fault reanalysis enables identification of the line of source code where the error occurred.

Note that only one program is compiled in each job step. This limitation is to facilitate the naming of the compiler listing data set member in accordance with the rules outlined in Naming compiler listings or side files.

You can optionally add an IDIOPTS DD statement to your JCL. This statement supplies the name of a sequential file containing Fault Analyzer options, providing job step overrides of product and installation defaults.

Other DD statements that you can add into your JCL are described in Pointing to listings with JCL DD statements.

Any options that are specified in the JCL EXEC statement PARM field override options set via the IDIOPTS file.

For more information, see User options file IDIOPTS.