You can display the statement execution counts in the Program Listing area to see how many times a statement was executed during a debug session.
For CA InterTest batch, execution counts are automatically turned on at the beginning of the debug session for every monitored program.
For CA InterTest CICS, you must turn the execution counts feature on for each program, if you want all the execution counts to be updated. For more information, see Set the Program Debug Settings for a CICS Program.
To display execution count in the Program Listing area
The Program Listing area displays a vertical shaded band. If you right-click again, you will see a check next to Show Execution Counts indicating that the ruler is visible. When you start a debug session, the execution count of each statement shows the vertical shaded band. The vertical shaded band shows different color backgrounds when the executable statements are located.
When first displayed the counts ruler displays zeroes if the debug session is inactive or at the first statement of an active debug session. If the debug session is already in progress, then the counts ruler is updated with execution counts up to the point of displaying the ruler.
The ruler is updated when each breakpoint is encountered. The number next to a statement represents the number of times that particular statement has executed up to that breakpoint.
When a program is halted at a breakpoint, you can reset the counts in the ruler by selecting Reset Execution Counts.
This action leaves the counts ruler visible but resets all the statement counts to zero.
In CICS, execution counts are disabled and hence reset, when a program is unmonitored.
Note: Initiating the execution counts feature at the beginning of a debug session does not automatically display the execution count ruler; both are separate actions.