Storage violations can be divided into two classes, namely those detected and reported by CICS®, and those not detected by CICS. They require different problem determination techniques.
CICS-detected violations are identified by the following message sent to the console:
DFHSM0102 applid A storage violation (code X'code') has been detected by module modname.
If you have received this message, turn first to the description of message DFHSM0102 in CICS Messages and Codes to see an explanation of the message, and then to CICS Trace Entries to see an explanation of the exception trace point ID, X'code'. This tells you how CICS detected the storage violation. Then return to this section, and read CICS has detected a storage violation.
Storage violations not detected by CICS are less easy to identify. They can cause almost any sort of symptom. Typically, you might have got a program check with a condition code indicating ‘operation exception’ or ‘data exception’, because the program or its data has been overlaid. Otherwise, you might have obtained a message from the dump formatting program saying that it had found a corrupted data area. Whatever the evidence for the storage violation, if it has not been detected by CICS, turn to Storage violations that affect innocent transactions.