Breakpoint Activities › Work with Data at a Breakpoint

Work with Data at a Breakpoint

When CA InterTest for CICS detects a breakpoint, it halts the program before the instruction at the breakpoint location is executed. While at a breakpoint, CA InterTest for CICS preserves the task's main storage for examination or modification prior to task resumption. Here is a summary of how to work with your data at a breakpoint. Each function is explained in this chapter.

• View or Search for Data

  View any portion of your compiler output and search for occurrences of data strings.

• Keep Data in Window

  Keep the values of data items, displayed up to 6 at a time, at the top of your source listing in the Keep window. This lets you observe changes in their values as the program executes without having to leave the source listing display.

  When the Keep window is active, the header lines listing the CA InterTest for CICS options and PF key functions are replaced with a command line. To view options and PF keys, press PF4, then press Enter to return.

• Code Coverage Counters in Window

  Display a counter for each line of code and check its verb execution count. This lets you observe changes in the execution value as the program executes without having to leave the source listing display.

• Display or Modify Main Storage

  Display and dynamically change data in main storage at any breakpoint. If there is an error, fix it in main storage, and then continue execution as if the error never existed.

  Online access to main storage means you do not have to wait for and analyze a dump. To make accessing main storage easy, CA InterTest for CICS provides a structured display of main storage with data names on the left and both hexadecimal and character values on the right.

• Display or Modify Auxiliary Storage

  View, modify, or create test data using the FILE transaction. At a breakpoint, verify test data, and even create test records.

For more information:

Accessing Auxiliary Storage: FILE