Previous Topic: How to Control the Flow of ExecutionNext Topic: How to Identify Indirect Commands on the Monitoring Status Display


Attach the Indirect Command to Breakpoints

To have the indirect commands automatically executed by your program, set an unconditional, conditional, or request breakpoint that points to the first indirect command statement number. When you set a breakpoint with this option, each time the breakpoint takes effect the indirect commands execute.

From the Source Listing facility, set the unconditional or conditional breakpoint as follows:

  1. Display the line in your Source Code where you want to set the breakpoint to execute the indirect commands.
  2. Type BPO in the command line or 12 in the Option # field (Breakpoint Options), tab down to the line where you want to set the breakpoint, type u for unconditional or c for conditional, and press Enter. The Breakpoint Locations menu appears, letting you set a number of breakpoint options.
  3. Tab to the following option near the bottom of the panel:
    Statement no. of indirect command(s) to be executed:     _____
    
  4. Type the first indirect command statement number (leading zeroes are optional), as shown in the following screen.

    CA InterTest MONITORING COMMAND BUILDER - PL/I BREAKPOINT LOCATIONS 11 SET breakpoint options for PROG=PLIDEMO for location: 635.1 1 NOPROB: After: _ All Procedure Names: _ Enter 'n' to stop only every n'th time: ____ Term ID (or .ANY or .NO) where breakpoints will take effect: U057 Term ID (or .ANY) that will receive the breakpoints: U057 Statement no. of indirect command(s) to be executed: 10__ User ID (or .ANY) who will execute the program: .ANY PF1 Help 2 3 End 4 Return 5 6 PF7 8 9 10 11 12

  5. Press Enter to process this menu.
  6. If you are setting a conditional breakpoint, type the condition on the Conditional Breakpoint screen and press Enter.

    Your Source Listing display shows the indirect command to execute on the line above the statement with the U or C indicator.

  7. To set a request breakpoint that executes an indirect command, follow the usual steps to set the request breakpoint from the menus. On the Request Breakpoint Selection menu, also type the statement number of the indirect command to be executed, as shown in the following screen.

    CA InterTest MONITORING COMMAND BUILDER ‑ REQUEST BREAKPOINT SELECTION 13 Set one or more types of Request Breakpoints in: PROG=PLIDEMO _ ALL commands _ DL/I _ DB2 _CALLs _ Address, Assign, _ Storage Control _ BMS Handles, Push, Pop _ Program Control _ Trace Control _ Terminal Control _ Interval Control _ Dump Control x 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 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: 100__ User ID (or .ANY) who will execute the program: ________ PF1 Help 2 3 End 4 Return 5 6 PF7 8 9 10 11 12