During an active monitoring session, if InterTest for CICS detects a potential problem with an application program, it will stop program execution and issue an Automatic Breakpoint (ABP) .
One such example is when a program attempts to write to the CICS Common Work Area (CWA); an area of storage defined within a CICS region that any user application can potentially utilize. Although the CWA can be considered a "public" area, while monitoring a program with InterTest, any attempt to write to this area will be perceived as a potential storage violation. In such a situation, InterTest will stop program execution and issue an automatic breakpoint. Any attempts to continue will be prevented unless the programmer takes some sort of corrective action.
My program will write data to the CICS CWA and never have a problem when it is not being monitored with InterTest. However, when the program is monitored, InterTest issues an automatic breakpoint, displays a message "About to change an area that does not belong to this task", and will not let the program continue. How can this problem be prevented?
InterTest offers different methods to allow programs to write to the CWA.
Depending upon the needs of the applications in use, these options can be used individually or in conjunction with each other to remove InterTest protection from this area.
Refer to the CA Intertest and Symdump r 10 documentation wiki for information on both the
Information on the CICS CWA can be obtained from the IBM Knowledge Center, CICS Transaction Server description of Storage Protection