Previous Topic: Set an Unconditional Breakpoint for a LabelNext Topic: Composite Support

PL/I Advanced Demo Session › Demo Preliminaries › How to Set Request Breakpoints

How to Set Request Breakpoints

You can set request breakpoints to halt a program before CICS commands and macros and other calls, such as calls to DL/I or DB2. You can set request breakpoints prior to all CICS commands (as you might have done with IBM's CEDF) or prior to specific commands, such as File Control or Program Control commands. Request breakpoints make it easy for you to halt your program at various points so you can check program processing. For example, you can halt the program before every READ command, single‑step through the read instructions, and then check main storage to make sure the program has read the correct record.

For option 03 of the advanced demo session, you need to set request breakpoints at all File Control REWRITE commands in the demo program. To do this, access the Request Breakpoint Selection menu.

  1. Press PF6 to return to the Primary Option Menu.
  2. Select 2 Monitoring.

    The Monitoring Menu appears.

  3. Select 1 Programs.

    The Program Monitoring screen appears.

    ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ CA InterTest Release 9.1.00  PROGRAM MONITORING  ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
 COMMAND ===>                                                                   
                                                                                
   Type information and S to set or R to remove option(s) below.               
                                                                                
   Program  . . PLIdemo_     Program name (or .ALL, .OPTIONS or generic)        
   User ID  . .     ____     User (or .ANY) for whom the program is monitored   
                                                                                
   Option       Description                                            More:   +
 _ Status       Display and/or remove monitoring options (S only)               
 _ Monitor      Monitoring (R removes monitoring and all options previously set)
 _ UBP          Unconditional breakpoints (specific program only)               
 _ CBP          Conditional breakpoints (specific program only)                 
 s RBP          Breakpoints for CICS, DB2, DL/I or external CALL requests       
 _ Stmt Trace   Statement tracing and data monitoring (COBOL only) 
 _ New copy     Fetch new copy of program and reset monitoring options (S only) 
 _ Commands     Indirect commands defined for a specific COBOL or PL/I program 
 _ Replace      CICS resource name replacement options                          
 _ Protect      Storage protection monitoring options                          
 _ Special      Other options (storage allocation, file updating, etc.)         
 _ Composite    Monitor multi‑CSECT program's separately compiled components 
                                                                                
 PF1 Help       2            3 End        4 Return     5            6     
 PF7 Backward   8 Forward    9           10           11           12
  4. In the Program field, type the name of the program for which you want to set a request breakpoint.
  5. Type an s to the left of RBP (request breakpoints) and press Enter.

    The Request Breakpoint Selection menu appears on which you specify the type of request breakpoint, such as all CICS commands, File Control, Task Control, and so on.

  6. Tab to the File Control field and type an s.
  7. Press Enter. 
    CA InterTest MONITORING COMMAND BUILDER - REQUEST BREAKPOINT SELECTION  13
                                                                               
             Set  one or more types of Request Breakpoints in:                 
                               PROG=PLIDEMO                                    
                                                                               
_ ALL commands                    _ DL/I              _ CALLs                  
                                                                               
  _ Address, Assign,         _ Storage Control    _ BMS                        
      Handles, Push, Pop     _ Program Control    _ Trace Control              
  _ Terminal Control         _ Interval Control   _ Dump Control               
  s File Control             _ Task Control       _ Batch Data Interchange     
  _ TD Control               _ Journal Control    _ Built-In Functions         
  _ TS Control               _ Syncpoints         _ Sys Prog Functions         
  _ Web access               _ Business Trans     _ 3270 Bridge                
  _ Channel/Container                                                          
                                                                               
  Enter 'n' to stop only every n'th time:                         ____         
  Term ID (or .ANY or .NO) where breakpoints will take effect:    ____         
  Term ID (or .ANY) that will receive the breakpoints:            ____         
  Statement no. of indirect command(s) to be executed:            _____        
  User ID (or .ANY) who will execute the program:                 ________     
                                                                               
PF1 Help       2            3 End        4 Return     5            6           
PF7            8            9           10           11           12

    The File Control Request Breakpoint Selection menu appears.

  8. On this menu you can select the specific File Control commands where you want to set request breakpoints. In this case, select REWRITE to halt the program prior to each File Control REWRITE command.
  9. Tab to the REWRITE command field.
  10. Type an s and press Enter. 
    CA InterTest for CICS MONITORING COMMAND BUILDER ‑ REQUEST BREAKPOINT SELECTION 
                                                                                
            Set  one or more types of File Control COMMANDS IN:                 
                                PROG=PLIDEMO                                    
                                                                                
              _ All commands                                                    
                                                                                
                    _ READ                                                      
                    _ WRITE                                                     
                    s REWRITE                                                   
                    _ DELETE
.
.
.

    CA InterTest for CICS sets request breakpoints prior to each File Control REWRITE command in the demo program and redisplays the Program Monitoring Menu.

The next topic is necessary only if you want to use the composite support option. Composite support is a CA InterTest for CICS feature designed to aid programmers who are responsible for testing and debugging called subroutines.