Specify Breakpoint Options

The following specifications are optional:

Enter 'n' to stop only every n'th time: Specifies how often the program should be halted when you set a breakpoint within a loop.
Term ID (or .ANY or .NO) where breakpoints will take effect: Specifies 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.
Term ID (or .ANY) that will receive the breakpoints: Specifies 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.
Statement no. of indirect command(s) to be executed: Specifies the statement number of the indirect command that you want to invoke at the breakpoint you have set.
User ID (or .ANY) who will execute the program: Specifies 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.