There are six types of breakpoints, as shown following:
The program stops because CA InterTest for CICS detected and prevented an error.
The program stops at the location you specify.
The program stops at the location you specify if a condition is met. Optionally, conditional breakpoints can be set to stop at any instruction if a condition is met.
The program stops whenever the value of a specified variable has changed.
The program stops at every CICS command or macro, or at certain CICS commands or macros, or at calls to DL/I, DB2, or software.
The program stops after executing one or more instructions.
An automatic breakpoint occurs when CA InterTest for CICS detects an error. When a program is stopped at an automatic breakpoint, you can either correct the error or go around it. You can press PF1 for help on what caused the error and how to use CA InterTest for CICS to fix it. You set the other breakpoints.
In this chapter we explain how to set and remove unconditional breakpoints as well as variable-change breakpoints, because you use them the most. For information on conditional and request breakpoints, see the next chapter. For more information on Single‑stepping, see Resume Program Execution.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|