Set request breakpoints to halt a program prior to CICS commands, macros, and other program calls, such as calls to DL/I, DB2, or SQL/DS. Instruct CA InterTest for CICS to halt the program before every CICS command, or a type of CICS command, such as file control or program control commands. Specify that the program halts before specific commands, such as all READ or WRITE commands. Once the program halts, Use all of the CA InterTest for CICS facilities to inspect and modify main storage or auxiliary storage or to set additional options.
To set or remove request breakpoints:
CA InterTest for CICS displays the Request Breakpoint Selection menu. Enter an x next to the options you want to select.
CA InterTest MONITORING COMMAND BUILDER REQUEST BREAKPOINT SELECTION 13 Set one or more types of Request Breakpoints in: PROG=COBDEMO Œ _ ALL commands _ ALL macros Ž_ 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 _____
Œ
The program halts prior to all CICS commands.
The program halts prior to all CICS macros.
Ž
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 halts prior to calls to software that CA InterTest for CICS has been instructed to recognize at installation time. A second screen opens for you to specify the calls.
‘
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 how often the program should halt. 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. If you leave this field blank, it defaults to your current terminal. 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. If you leave this field blank, it defaults to your current terminal. Enter .ANY to have breakpoint screens displayed at the terminal where the program is executing when breakpoints occur.
•
Specify the first indirect command statement number to take effect at this breakpoint.
Specify the CICS user ID of the user (or .ANY) who must execute the program for the breakpoint to take effect.
Note: Your version of this screen might differ slightly, depending on CA InterTest for CICS installation options.
When you have entered all necessary information, press Enter. If you entered an x next to a type of command, CA InterTest displays a second screen.
Example
If you selected File Control as the previous screen shows, 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
On 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.
To remove request breakpoints, use the Monitoring Status display.Alternatively, enter the information exactly as you originally defined it.
|
Copyright © 2012 CA.
All rights reserved.
|
|