PL/I 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, perform the following procedure:

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

   The following screen shows how to set a breakpoint.

   CA InterTest for CICS Release 9.1.00   - PROTSYM FILE  SOURCE LISTING DISPLAY            
   COMMAND ===>                                                                    
   Program= PLIDEMO  Option #      Stmt #                             Margin= 01  
                                           Search=                        
   OPTS 1 Data xref 2 Aggregate 3 Stor reqs  4 Stat stor  5 Var stor   More:   +   
        6 Offsets   7 Gend code 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    
   ---------+--------------------------------------------------------------------- 
    _   637.1               MAPNUM  = '00';                                        
    _   638.1     1         TASKNUM = TASKNUM + 1;                                 
    _   639.1     1         IF TASKNUM > 2 THEN                                    
    _   640.1     1            GOTO END_SESSION;                                   
    u   641.1     1         IF TASKNUM = 1 THEN                                    
    _   642.1     1            GOTO SENDSCR3;                                      
    _   643.1     1         GOTO END_SESSION;  
   .
   .
   .                                          
   

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

   You can set breakpoints at any time; either before executing the program or 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:

   • At the beginning of the program, so when the program executes you can set additional breakpoints
   • At labels, 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 want to remove breakpoints no longer needed so that when retesting the program, you are not unnecessarily stopped.