COBOL Debugging Programs › Set and Remove Breakpoints › Set Unconditional Breakpoints at Statements on the Source Listing

Set Unconditional Breakpoints at Statements on the Source Listing

To set an unconditional breakpoint on the program source listing, follow these steps:

1. Typer u in column 1 next to the statement where you want the breakpoint.
2. Press Enter.

   The following screen shows how to set an unconditional breakpoint.

      CA InterTest for CICS V9.1   - PROTSYM FILE  SOURCE LISTING DISPLAY        
   COMMAND ===>                                                                    
   Program= COBDEMO  Option #       Stmt #                             Margin= 01  
                                           Search=                                 
   OPTS 1 Proc div  2 Work-stor 3 Link sect  4 D-map      5 Clst/Pmap More:   +    
        6 Data xref 7 Proc xref 8 Err msgs   9 Srch fwd  10 Srch bwd               
   PFKS 1 Help      2           3 End        4 Profile    5 Monitor    6 Menu      
        7 Backward  8 Forward   9           10           11           12 Status    
   ------------------------------------------------------------------------------- 
    _ 000475     IF EIBAID = DFHPF14  GO TO EXPANDED-DEMO.                         
    _ 000476     GO TO SEND-FIRST-SCREEN.                                          
    _ 000477 CONTINUE-TASK.                                                        
      000478**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED                          
    _ 000479     ADD +1 TO TASKNUM.                                                
    u 000480     IF TASKNUM = 1  
   .
   .
   .                                                 
   

   After you set a breakpoint, CA InterTest redisplays the screen with the U in uppercase. The U remains until you remove the breakpoint.

   You can set breakpoints at any time—before you execute the program and when the program is stopped. Although where you decide to set breakpoints depends on the specifics of your program, you might want to set breakpoints in the following places:

   • At the beginning of the Procedure Division, so when the program executes you can set additional breakpoints
   • At paragraph names, so you can examine the contents of variables at the start of sections
   • Before a call, so you can dynamically control the program path
   • At each location named in an EXEC CICS HANDLE CONDITION, so you can verify error handling

   To remove an unconditional breakpoint, overtype the U with an x, or type an r next to the breakpoint's entry on the Monitoring Status display (PF12 from Source Listing). You will want to remove breakpoints no longer needed so that when retesting the program, you are not stopped unnecessarily.