CNTL Commands and Menus › Initiate Monitoring › Unconditional Breakpoints › Set Unconditional Breakpoints

Set Unconditional Breakpoints

Use the Breakpoint Locations screen t to set unconditional breakpoints.

To set breakpoints, enter the following information:

Specify up to nine breakpoint locations in fields.

COBOL

For COBOL program, specify a paragraph name or data name, a statement number, or the hexadecimal displacement (offset) from the beginning of the program.

ASSEMBLER

For an Assembler program, breakpoint locations are Assembler labels, datanames, or offsets.

PL/I

For a PL/I program, breakpoint locations can be offsets or, if you have the PL/I symbolic option, PL/I labels or statement numbers.

Follow these rules when specifying information:

• If you specify statement #1, CA InterTest for CICS sets a breakpoint at the first executable instruction in a COBOL Procedure Division, Assembler CSECT, or PL/I procedure.
• COBOL statements can contain more than one verb. In specifying statement numbers, indicate the verb at which the breakpoint should occur. A statement number of nnn or nnn.0 indicates the first verb in the statement, nnn.1 indicates the second verb, nnn.2 indicates the third verb, and so on. For example, a statement number entered as 503.3 specifies a breakpoint at the fourth verb in statement number 503.
• If you specify a COBOL or Assembler data name, breakpoints are set at every reference to that data name.
• Enter an X in the All paragraph names field (COBOL) or All Assembler labels field to set breakpoints at all paragraph names or all labels.

Optional specifications:

• If you set a breakpoint within a loop, specify a value in the Enter 'n' to stop only every n'th time field to set how often the program should be halted. For example, if you specify 3, the breakpoint occurs every third time the program passes through the loop.
• 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 statement number of the indirect command that you want to invoke at the breakpoint you have set.
• Specify the user ID who must be executing the program for the breakpoint to take effect. Valid entries are .ANY or a specific CICS user ID.

When you complete entering all the necessary information, press Enter.

For more information:

Accessing Main Storage: CORE