Reporting › Reports

Reports

Four reports are described in this chapter. The Execution Monitor produces two reports, the CAIOPTS File Processing Report and the Execution Monitor Summary. The Execution Monitor is the component of CA SymDump Batch that establishes the reporting environment. The CAIOPTS File Processing report displays the input options you specified to control abend or Snap reports. The Execution Monitor Summary displays the options in effect at the time the report was generated.

The following list describes the abend and Snap reports:

• The abend report is printed whenever an ABEND occurs during program execution. The report contains the following:
  • Diagnostic information based on the type of ABEND.
  • The COBOL, PL/I, or Assembler source statement on which the ABEND occurred, if symbolic information for the abending program was available. Otherwise, the machine instruction and its operands are displayed.
  • The names and values of the data items referenced by the abending statement are also displayed if symbolic information is available from a PROTSYM file, or from a CSL file if MXREF was specified when the CSL member was created.
  • Addresses and other specifics pertinent to the ABEND.
  • The module call sequence showing the hierarchy of programs that invoked the abending program.
  • The contents of the abending program's registers at ABEND.
  • Formatted data displays of all program variable fields, if symbolic support is available. For COBOL, this includes Working Storage, Local-Storage, Linkage and File Sections. For PL/I, this includes all variables for all active procedures and a dump of both static and external program storage. For Assembler, this includes storage mapping of all addressable storage from the USINGs in effect at the abending statement and a dump of all unmapped addressable storage. If symbolic support is not available, all data areas are displayed in standard dump format.
  • A standard dump display of the program-level control blocks. For COBOL, this includes the PGT, TGT, and DSA. For PL/I, this includes the DSA for each active procedure.
  • An optional display of the memory map (TGT, PGT, DSA).
  • The data control blocks of all open files not reported on in the FILE SECTION (optional).
  • The Save Area Trace report showing the standard chain of register areas (optional).
• The Snap report provides you with a snapshot of your program at strategic points during execution. The Snap report contains the same information as the abend report with the exception of the data identifying the ABEND and the module call sequence. To produce a Snap report, you must do the following:
  • Insert a call to program CAODSNAP.
  • Specify the SNAP ON option at execution time.

  Note: Each call to CAODSNAP generates a separate Snap report in your central VSAM repository. If your program contains multiple snap calls (or a snap call within a loop), you may want to write the output to the CAIPRINT DD alone, to avoid flooding the repository. For more information, see the PRTREPT option in Using Options.