Set Request Breakpoints from the Menus

Using Breakpoints › Request Breakpoints › Set Request Breakpoints from the Menus

Set Request Breakpoints from the Menus

When viewing a program listing before or after a breakpoint, specify the RBP command to display the RBP menus.

Alternatively use the Program Monitoring (2.1), Transaction Monitoring (2.2), or Terminal Monitoring (2.33) menu to set request breakpoints. Complete the top of the menu according to how you are monitoring or want to monitor the program, terminal, or transaction, and select the RBP option on the bottom of the menu. Detailed steps on how to do this are given next for users unfamiliar with the monitoring menus.

Access the Primary Option Menu, and select 2 Monitor to access the Monitoring Menu.
Select option 1 Program to have the request breakpoints apply to a monitored program. Alternatively, select another monitoring option if you are monitoring by Transaction (2) or Terminal (2).
On the Monitoring submenu, complete the monitoring entry for the Program (Terminal or Transaction) and user ID, and then type s next to the RBP Option for Request Breakpoints and press Enter.

The following screen shows how to complete the Program Monitoring Menu (2.1) to set request breakpoints for the COBDEMO program being monitored for the user ID BARNEY1.

-------------- CA InterTest r8.5 PROGRAM MONITORING ---------------------- COMMAND ===> Type information and S to set or R to remove option(s) below. Program . .cobdemo_ Program name (or .ALL, .OPTIONS or generic) user ID . .barney1_ User (or .ANY) for whom the program is monitored More: + Option Description _ 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 PF1 Help 2 3 End 4 Return 5 6 PF7 Backward 8 Forward 9 10 11 12

After specifying the RBP command from the Source Listing screen or completing the monitoring menu with the RBP option selected, CA InterTest for CICS displays the Request Breakpoint Selection menu.

CA InterTest MONITORING COMMAND BUILDER REQUEST BREAKPOINT SELECTION 13 Set one or more types of Request Breakpoints in: PROG=COBDEMO Œ _ 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 _ BuiltIn Functions _ TS Control _ Syncpoints _ Sys Prog Functions 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: BARNEY1 • PF1 Help 2 3 End 4 Return 5 6 PF7 8 9 10 11 12

On this screen enter an x next to the options you want to select:

The program halts prior to all CICS commands.

The program halts prior to all DL/I calls.

The program halts prior to all calls to DSNHLI (for DB2 users) or prior to all calls to ARIPRDI (for SQL/DS users).

The program is halted prior to calls to software that CA InterTest has been instructed to recognize at installation time. A second screen, where you specify the calls, displays.

If you select a type of CICS command, CA InterTest for CICS displays a second screen. For example, if you select File Control, CA InterTest for CICS displays the File Control screen.

‘

If you do not want the program to halt before every occurrence of a command, specify in this field how often the program should be halted. For example, if you specify 3 the breakpoint occurs every third time the program reaches the command. This feature is especially useful when a CICS command occurs within a loop; for example, during a browse.

’

Specify the ID of the terminal where the program must be executing for breakpoints to take effect. You can generally leave this field blank and have the default location apply.

Enter .ANY to have breakpoints take effect at all terminals—even when the program executes without a terminal.
Enter .NO to have breakpoints take effect only when the program executes without a terminal.

“

Specify the ID of the terminal to receive breakpoint displays. You can generally leave this blank, and have the default location apply. Enter .ANY to have breakpoint screens displayed at the terminal where the program is.

”

Specify the first indirect command statement number to take effect at this breakpoint.

•

For secure CICS regions, specify the CICS user ID of the user who must be executing the program for the request breakpoints to take effect. If you do not have a secure CICS system, leave this blank.

Note: Your version of this screen may differ slightly depending on CA InterTest for CICS installation options.

When you have entered all of the necessary information, press Enter. If you entered an x next to a type of command, CA InterTest for CICS displays a second screen.

Example

If you selected File Control as the previous screen illustrates, CA InterTest for CICS displays the following screen.

CA InterTest MONITORING COMMAND BUILDER REQUEST BREAKPOINT SELECTION Set one or more types of File Control commands/macros in: PROG=COBDEMO _ All commands _ All macros è x READ è x WRITE _ REWRITE _ DELETE _ UNLOCK _ STARTBR _ READNEXT _ READPREV _ ENDBR _ RESETBR Enter 'n' to stop only every n'th time ____ PF1 Help 2 3 End 4 Return 5 6 PF7 8 9 10 11 12

Using this screen specify that the program be halted at all File Control commands or macros, or select specific File Control commands. In this example, the user specified that program COBDEMO be halted at all READ and WRITE commands.