

Using Breakpoints › Unconditional Breakpoints › Set Unconditional Breakpoints from the Menus › Specify Breakpoint Options
Specify Breakpoint Options
The following specifications are optional:
- If you set a breakpoint within a loop, specify in field ‘ how often the program should be halted.
Example
If you specify 3, the breakpoint occurs every third time the program passes through the loop.
- Specify in field ’ 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 in field “ 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 the breakpoints occur.
- Specify in field ” the statement number of the indirect command that you want to invoke at the breakpoint you have set.
- Specify in field • the CICS ID of the user who must execute the program for the breakpoint to take effect. Valid entries are a specific CICS user ID or .ANY. The default varies depending on your installation option settings for DFLTUSER.
- When you have entered all the necessary information, press Enter.
Copyright © 2012 CA.
All rights reserved.
 
|
|