PL/I Debugging Programs › Set and Remove Breakpoints › Types of Breakpoints

Types of Breakpoints

There are five types of breakpoints for PL/I programs:

• Automatic— The program stops because CA InterTest for CICS 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.
• 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 for CICS to fix it. You set all other breakpoints.

In this chapter we explain how to set and remove unconditional breakpoints, because you use these the most. For information on conditional and request breakpoints, see the chapter "Advanced Monitoring Features." Single‑stepping is discussed in Resume Program Execution.

The next sections explain how to do the following tasks:

• Set breakpoints at statements on the source listing
• Set breakpoints at all references to a data name
• Set breakpoints at all or selected paragraph names or labels