There are six types of breakpoints, as shown in the following table:
|
Breakpoint Type |
Function |
|
automatic |
The program stops because CA InterTest detected and prevented an error. |
|
unconditional |
The program stops at the location you specify. |
|
conditional |
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. |
|
variable‑change |
The program stops at any location if the value of a specified variable has changed. |
|
request |
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. |
|
single‑step |
The program stops after executing one or more verbs. |
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 to find out what caused the error and how to use CA InterTest to fix it. You set all other breakpoints.
In this chapter we are going to explain how to set and remove unconditional breakpoints as well as variable‑change breakpoints, because you will use these the most
For more information on conditional and request breakpoints, see the chapter "Advanced Monitoring Features". For more information on Single‑stepping, see Resuming Program Execution. The following sections explain how to set breakpoints:
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|