Programmed breakpoints (PBP) are intended primarily for users of PL/I who want to display data areas that CA InterTest for CICS normally cannot display or who do not have symbolic information for their programs. Incorporate programmed breakpoints into COBOL and Assembler code.
Programmed breakpoints differ from other CA InterTest for CICS breakpoints because they are actually coded by the programmer into the tested program. A programmed breakpoint occurs because it was written into the monitored program in the form of a special CALL statement that identifies the data areas to display. The Detailed Breakpoint display automatically shows, in dump format, up to three data areas named in the CALL statement parameters. There is no need to enter CORE commands to display these areas. However, if there are more than three data areas, use the command CORE=ARGnn to display them.
If you are using the Source Listing Breakpoint facility, CA InterTest for CICS stops the program at the programmed breakpoint. Press PF3 DET BKPT to display the Detailed Breakpoint screen to view the requested data areas.
The programmed breakpoint will not occur unless the automatic breakpoint facility is active. If this facility is not active, the programmed breakpoint CALL has no effect on program execution. The programmed breakpoint also does not affect program execution if the program is not monitored by CA InterTest for CICS (the called routine only does a return). However, a small amount of overhead is added to the program's execution. For this reason, programmed breakpoints should be removed before the program is put into production.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|