We will page back to find out what caused the error.
CA InterTest for CICS displays the following screen.
CA InterTest for CICS V9.1 - PROTSYM FILE ABEND DETECTED BREAKPOINT COMMAND ===> Program= COBDEMO Option # Stmt # Margin= 01 Search= ------------------------------------------------------------------------------- _____ NEW-DATA | .............V...... _____ STG-AREA1 | .................... ---------+--------------------------------------------------------------------- 000968**** NOW MOVE NEW DATA INTO ACQUIRED AREA 000969* A ==> MOVE NEW-DATA TO STG-AREA1. ==> ==> an attempt to change an area that does not belong to this task. ==> Possible system damage has been prevented. ==> ==> Press PF1 for a detailed description. ==> _ 000971 GO TO SEND-MAP00. _ 000972 WHICH-ONE. _ 000973 GO TO REPLACE-FILE _ 000974 MXR-OPTION _ 000975 READ-FOR-UPDATE _ 000976 SET-VAR-REC _ 000977 PROCESS-TABLE
Look at the FREEMAIN statement that releases the storage for STG‑AREA. Now it is lear why the storage violation occurred. The demo program released the storage for STG‑AREA. After releasing the storage, the program tried to move data to STG‑AREA1, which is part of STG‑AREA.
To correct the problem, you would have to remove the FREEMAIN statement or change its location, and then you would recompile the program. However, one of the benefits of CA InterTest for CICS is that you do not have to correct a problem when you discover it. Instead, you can go around the problem and continue testing the program.
Now we will redisplay the breakpoint.
CA InterTest for CICS redisplays the automatic breakpoint.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|