To help you test and debug CICS programs effectively, you can also interrupt program execution at any point by setting breakpoints. You can set four types of breakpoints:
Unconditional— the program stops when it reaches a specified location.
Conditional—the program stops when it reaches a specified location and a prescribed condition is met (for example, a variable exceeds a certain limit).
Variable‑change—the program stops at any location if the value of a specified variable has changed (COBOL and Assembler only).
Request—the program stops when it reaches specified CICS Commands, calls to DL/I or DB2, and calls to subroutines, such as database software.
You also can instruct CA InterTest for CICS to halt your program each time it executes a specified number of COBOL verbs, PL/1 statements, or Assembler instructions.
Controlling the pace at which a program executes makes it easier to pinpoint and correct logic errors. For example, when a program is halted, you can inspect the values of program variables and test data to determine whether processing is proceeding as planned. You can also dynamically change the value of a data item or generate additional test records before resuming execution.
When a program is stopped at a breakpoint, you can resume execution at any time and from any point. This means you can go around errors or dynamically alter the order in which certain routines are executed. When your program is halted at a breakpoint, you can do the following tasks:
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|