Can anybody help me out finding the real cause of the abend. Following I get from the dump. It seemed like that storage violation, but the same code is working in the some cases with different values but the same key.
A storage violation occurred. CICS detected that the storage at address
154B77E0 has an invalid storage zone. The leading storage zone is
E4F0F0F0F0F0F7F1 and the trailing storage zone is 4040404040404040.
Addressability and matching information are available for the area.
The current task at the time the dump was taken was 71.
The CICS trace table has 1 exception entry, and it is related to task 71.
The exception trace entry for task 71 gives the following information:
00071 QR SM 0D11 SMMF *EXC*
The CICS Kernel Error Table had no entries.
There are 2 CICS enqueues held, with no tasks waiting.
There are no tasks waiting for storage.
No programs where changed within the last 14 days.
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
If you post more info about the task that is abending, someone may have a suggestion.
What is the tran-id? Who wrote this code? Is the abend in a business application or some utility function? It sounds like the task is trying to "give back" memory it has not acquired.
While the code may not have changed, have any control parameters changed (either to the system or this set of code in particular)? Is there another transaction that reads the same data that works or does everything trying to read a "problem" key in this file have problems?
There is very little that we can do from the forum...
ask system support to look at the dump ( the only thing to do in such cases )
in the hope that looking at the data contained in the overlaid section somebody might get a hint on the transaction guilty for the overlay