Debugging Programs › Keep Variables in the Keep Window › View the Variable-Change Breakpoint

View the Variable-Change Breakpoint

The uppercase V that appears to the left of the highlighted statement easily identifies a breakpoint display as a variable-change breakpoint, as shown in the following panel:

CA InterTest for CICS Release 9.1.00   - PROTSYM FILE   COND  BEFORE  BREAKPOINT         
COMMAND ===>                                                                    
Program= ASMDEMO  Option #       Stmt #        Displacement=        Margin= 01  
                                        Search=                                 
------------------------------------------------------------------------------- 
 _____ R13.TASKNUM                     | +00001.                                
---------++-------------------------------------------------------------------- 
     Loc  Object Code    Addr1 Addr2  Stmt        Source Statement              
 _ 000196 FA20 D189 4AE8 00189 02AE8  1457          AP    TASKNUM,=P'1'         
 V 00019C F920 D189 4AE9 00189 02AE9   ==>          CP    TASKNUM,=P'2'         
     ==>                                                                        
     ==> CAIN3630 Conditional breakpoint    requested at offset .ANY            
     ==> IF='R13.TASKNUM'.NE.'R13.TASKNUM'                                      
     ==>                                                                        
 _ 0001A2 4720 2328            00328  1459          BH    ENDMSG                
 _ 0001A6 F920 D189 4AE8 00189 02AE8  1460          CP    TASKNUM,=P'1'         
 _ 0001AC 4780 227E            0027E  1461          BE    SENDSCR4              
 _ 0001B0 47F0 2328            00328  1462          B     ENDMSG                
 _ 0001B4                             1464 RETURN   DS    0H                    
                                      1465 *        EXEC CICS SEND FROM(OUTMSG  
                                      1466          DFHECALL =X'04043000080000  
   0001B4 4110 D068            00068                      ),(FB_2,OUTLEN)       
                                      1482 *        EXEC CICS SEND FROM(SCREEN  
                                      1483          DFHECALL =X'04043000080000

The lines below the highlighted line further identify the breakpoint. If you set more than one variable-change breakpoint, this information lets you know which variable triggered the breakpoint.

Why does the breakpoint display refer to this as a conditional breakpoint? Because a variable-change breakpoint is actually a special type of conditional breakpoint. The condition CA InterTest for CICS checks for, at ANY statement, is shown as:

IF'data-item'.NE.'data-item'

This is interpreted as:

IF data-item (current) NOT EQUAL TO variable (value when breakpoint set)

To explore additional ways to use conditional breakpoints, see the chapter "Advanced Monitoring Features" or Advanced Demo Session. For more information on using conditional breakpoints, see the User Guide.