Review What Happened

In this part of the demo session you took advantage of several CA InterTest for CICS features. You were able to:

Use a request breakpoint to halt the demo program prior to the first File Control REWRITE command.
Request breakpoints make it easy for you to halt your program at various points, such as before all HANDLE CONDITION commands or all Terminal Control commands. When your program halts, you can inspect main storage or auxiliary storage to detect errors and review program logic.
Use the No File Updating option to prevent a program from updating a file.
Preventing a program from updating a file means you can test a program repeatedly without having to recreate test data. Many programs can share the same test file because no program will actually change it. A test program can even use a production file without corrupting it.
Display a record in a file.
Displaying a record in a file lets you see whether your program is working correctly. The FILE facility also lets you add, delete, and update records to meet your individual testing needs and maintain files without special one‑time programs.