SET TEST command

Overrides the initial TEST run-time options specified at invocation. The initial setting is ALL.

test_level

Specifies what exception conditions cause z/OS® Debugger to gain control, even though no breakpoint exists. The parentheses are optional.

Test_level can include the following:

ALL

Specifies that z/OS Debugger gains control when any of the following conditions occur:

• An attention interrupt occurs.
• A Language Environment® enclave is abnormally terminated or there is an MVS or CICS® ABEND when a program is running without the Language Environment run time.
• Language Environment terminates normally due to a COBOL STOP RUN, PL/I STOP, or EXEC CICS RETURN.
• Language Environment raises a condition of severity 1 or above. If the FINISH, CEE066 or CEE067 thread termination condition is raised by Language Environment and the EQAOPTS THREADTERMCOND command is specified, z/OS Debugger does not gain control. You or your system administrator can specify this command by creating an EQAOPTS load module or providing the command at run time.

If a condition occurs and a breakpoint exists for the condition, z/OS Debugger runs the commands specified in the breakpoint. If a condition occurs and a breakpoint does not exist for that condition, or if an attention interrupt occurs, z/OS Debugger does one of the following options:

• In interactive mode, z/OS Debugger reads commands from a commands file (if it exists) or prompts you for commands.
• In noninteractive mode, z/OS Debugger reads commands from the commands file.

ERROR

Specifies that only the following conditions cause z/OS Debugger to gain control without a user-defined breakpoint.

• An MVS or CICS ABEND that occurs when you are running without the Language Environment run time
• For C:
  • An attention interrupt
  • A predefined Language Environment condition of Severity 2 or above
  • Any C condition other than SIGUSR1, SIGUSR2, SIGINT or SIGTERM.
• For COBOL:
  • An attention interrupt
  • A predefined Language Environment condition of Severity 2 or above.
• For PL/I:
  • An attention interrupt, directed at either PL/I or z/OS Debugger
  • A predefined Language Environment condition of Severity 2 or above.

If a breakpoint exists for one of the above conditions, any commands specified in the breakpoint are executed. If no commands are specified, z/OS Debugger reads commands from a commands file or prompts you for commands in interactive mode.

NONE

Specifies that z/OS Debugger gains control only at an attention interrupt, or at a condition if a breakpoint is defined for that condition. If a breakpoint does exist for the condition, the commands specified in the breakpoint are executed.

Usage note

If the EQAOPTS THREADTERMCOND command prevents z/OS Debugger from stopping when a FINISH, CEE066, or CEE067 thread termination condition is raised by Language Environment, z/OS Debugger does not gain control when these conditions are raised. If you want z/OS Debugger to gain control when these conditions are raised, you can set an AT OCCURRENCE breakpoint or change the EQAOPTS THREADTERMCOND command to allow z/OS Debugger to gain control.

Examples

• Indicate that only an attention interrupt or exception causes z/OS Debugger to gain control when no breakpoint exists.

  SET TEST ERROR;

• Indicate that no condition causes z/OS Debugger to gain control unless a breakpoint exists for that condition.

  SET TEST NONE;

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

• Related tasks
• IBM® z/OS Debugger User's Guide
• Related references
• AT OCCURRENCE command
• z/OS Language Environment Debugging Guide