Recording your debug session in a log file

z/OS® Debugger can record your commands and their generated output in a session log file. This allows you to record your session and use the file as a reference to help you analyze your session strategy. You can also use the log file as a command input file in a later session by specifying it as your primary commands file. This is a convenient method of reproducing debug sessions or resuming interrupted sessions.

The following appear as comments (preceded by an asterisk {*} in column 7 for COBOL programs, and enclosed in ⁄* *⁄ for C, C++, PL/I and assembler programs):

  • All command output
  • Commands from USE files
  • Commands specified on a __ctest() function call
  • Commands specified on a CALL CEETEST statement
  • Commands specified on a CALL PLITEST statement
  • Commands specified in the run-time TEST command string suboption
  • QUIT commands
  • z/OS Debugger messages about the program execution (for example, intercepted console messages and exceptions)

Refer to the following topics for more information related to the material discussed in this topic.