IBM Mainframe Forum

Hi Friends,

I need some help on Storage Violation. is there any way we can track the address where storage violation is occurring. This is the message getting displayed in logs



Problem is we don't know at which scenario this SV is coming and DFHMEME is a image program of a source code.

Check with your CICS support group.

One of the reasons to get your CICS support group involved is that a storage violation may be detected a long time after the storage was written, which makes finding and resolving the problem much more difficult. And there are multiple reasons for storage violations (table overflows in application code, copy book changes, inter-program issues are just three of them) so resolving your problem is not merely a matter of looking for issue X.

Thanks Robert and Nicc,

Basically the problem with storage violation is that you get to know once transaction is over. I have CEDX, but somehow it is not useful for debugging storage violation issues. Somehow, today I had to identify the exact program and location where storage violation was occurring, by commenting and un-commenting para by para in main program which was very much time consuming.

The actual issue was we were allocation space for response, using GETMAIN for certain length, however the response we were getting from LINKed program was larger than allocated. I was just going through some IBM manuals where CETR was suggested for storage violation with proper steps, however I will be needing some more suggestions on how can we deal with Storage Violation efficiently and most important quickly..

Is this, http://www-01.ibm.com/support/docview.w ... 7891&aid=1, any good to you?

Hi Billy,

Thanks for the doc. Now I have little bit clarity about how CICS works for Storage Violation. Currently not getting any SV issue, but will try yo apply the info next time. Thanks again.