Notes on debugging in batch mode

Note: This chapter is not applicable to IBM® Developer z/OS® (non-Enterprise Edition) or IBM Z and Cloud Modernization Stack (Wazi Code).

z/OS Debugger can run in batch mode, creating a noninteractive session.

In batch mode, z/OS Debugger receives its input from the primary commands file, the USE file, or the command string specified in the TEST run-time option, and writes its normal output to a log file.

Note: You must ensure that you specify a log data set.

Commands that require user interaction, such as PANEL, are invalid in batch mode.

You might want to run a z/OS Debugger session in batch mode if:
  • You want to restrict the processor resources used. Batch mode generally uses fewer processor resources than interactive mode.
  • You have a program that might tie up your terminal for long periods of time. With batch mode, you can use your terminal for other work while the batch job is running.
  • You are debugging an application in its native batch environment, such as MVS/JES or CICS® batch.

When z/OS Debugger is reading commands from a specified data set or file and no more commands are available in that data set or file, it forces a GO command until the end of the program is reached.

When debugging in batch mode, use QUIT to end your session.

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