Using CA InterTest for CICS to Find Errors

If you also have CA InterTest for CICS, you can use it to locate errors. This chapter explains how to locate errors using CA InterTest for CICS.

The example in this chapter lets you find and correct the error without re-executing the program. However, sometimes you will want to monitor the program with CA InterTest for CICS to learn more about what caused the error. You can turn monitoring on directly from the Source Listing Dump Analysis screen by entering MONITOR in the command line or pressing PF5. You can also set breakpoints or other monitoring options from this display, and then all you have to do is exit from CA SymDump for CICS and re-execute the transaction.

When CA InterTest for CICS halts the program at an automatic breakpoint or at a breakpoint you set, you can use the full power of CA InterTest for CICS to debug the program. For example, you can:

Examine the backtrace to determine the logic flow up to that point
Dynamically correct the problem and resume execution

With both CA SymDump for CICS and CA InterTest for CICS, you have all the tools you need to find and correct a problem.

This section contains the following topics:

View the Breakpoint at the Triggering Source Statement

Redisplay the Abend

Locate Where TASKNUM Was Initialized