Writing the TEST runtime option string

The instructions in this section apply to programs that run in Language Environment®. For programs that do not run in Language Environment, refer to the instructions in Starting z/OS Debugger for programs that start outside of Language Environment.

This topic describes some of the factors that you need to consider when you use the TEST runtime option, provides examples, and describes other runtime options that you might need to specify. The syntax of the TEST runtime option is described in the topic “TEST run-time option” in IBM® z/OS Debugger Reference and Messages.

To specify how z/OS Debugger gains control of your application and begins a debug session, use the TEST runtime option.

The simplest form of the TEST option is TEST with no suboptions specified. If Debug Profile Service is active, a simple TEST option enables delay debug mode, regardless of whether the DLAYDBG EQAOPTS command is in effect. z/OS Debugger acquires the naming pattern for the delay debug data set from the profile service. For more information about this behavior, see Simple TEST option.

If you choose a more detailed TEST option, suboptions provide you with more flexibility. There are four types of suboptions available:

test_level: Determines what high-level language conditions raised by your program cause z/OS Debugger to gain control of your program.
commands_file: Determines which primary commands file is used as the initial source of commands.
prompt_level: Determines whether an initial commands list is unconditionally run during program initialization.
preferences_file: Specifies the session parameter and a file that you can use to specify default settings for your debugging environment, such as customizing the settings on the z/OS Debugger Profile panel.