This section of the demo session shows you how to execute a program without having it update a file.
The No File Updating option is very useful when you are testing a program. Preventing a program from updating a file means your test data will be unchanged at the end of each program execution so you can test the program repeatedly without having to create test data.
Many programs can use the same test file without interfering with each other's work. You can even allow a test program to use a production file because the integrity of the file will be preserved.
Before you begin this section, complete the steps outlined earlier in this chapter in the Startup section (unless you did so earlier in this session). The Options Menu appears. Also be sure that the CA InterTest for CICS checkpoint file (PROTCPF) is defined to your CICS region and that the file's current status is Open and Enabled.
ASMDEMO displays a screen that describes what will occur in this part of the demo session.
********************************************************************** **** **** **** CA InterTest Demo Session **** **** No File Updating Option **** **** **** ********************************************************************** The program reads a record and changes data in the record. Here is what will happen: 1. CA InterTest halts the program at a request breakpoint. 2. You set the No File Updating option to prevent ASMDEMO from updating the file. 3. When ASMDEMO rewrites the file, the file is not updated. 4. After the rewrite you use the FILE facility to confirm that the file has not been updated. When this section of the demo completes, you will return to the Options Menu. Press ENTER to continue or CLEAR to terminate
CA InterTest for CICS displays the Request Breakpoint screen.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|