If you want to set unconditional breakpoints, the Breakpoint Locations screen opens. COBOL, PL/I, and Assembler versions of the Breakpoint Locations screen are available. The following screen is the COBOL version.
CA InterTest MONITORING COMMAND BUILDER COBOL BREAKPOINT LOCATIONS 11 SET breakpoint locations for PROG=COBDEMO in any of the following fields: (For qualification by nested program name, specify 'ProgramID:Label') ŒPara/Data ___________________________ _______________________________ Names: ___________________________ _______________________________ ___________________________ _______________________________ Statement Numbers: ____ _____ _____ _____ _____ _____ _____ _____ Ž Offsets: ____ _____ _____ _____ _____ _____ _____ _____ All paragraph names: _ 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 ________ ” PF1 Help 2 3 End 4 Return 5 6 PF7 8 9 10 11 12
To set breakpoints, enter the following information:
Specify up to nine breakpoint locations in fields Œ through Ž.
COBOL
For a COBOL program, this is 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:
Example
A statement number entered as 503.3 specifies a breakpoint at the fourth verb in statement number 503.
Example
If you specify 3, the breakpoint occurs every third time the program passes through the loop.
When you complete entering all the necessary information, press Enter.
|
Copyright © 2012 CA.
All rights reserved.
|
|