Storage violations that affect innocent transactions
CICS® does not usually detect storage violations that affect innocent transactions; that is, transactions that do not cause the violation. However, CICS sometimes detects that the initial SAA of a TIOA element or the storage check zone of a user-storage element has been overlaid by a task that does not own it.
If they are reproducible, storage violations of this type typically occur at specific offsets within structures. For example, the start of an overlay might always be at offset 30 from the start of a field.
The most likely cause of such a violation is a transaction that writes data to a part of the DSAs that it does not own, or possibly that releases such an area by using a freemain request. The transaction might obtain the area by using a getmain request and then release it by using a freemain request before writing the data, or an application might not maintain addressability correctly in another way. Another possible reason is that a transaction posted an event control block (ECB) after the task that was waiting on it was canceled.
Storage violations that affect innocent transactions are generally more difficult to resolve than those that CICS detects. You might not become aware of them until some time after they occur, so you need a long history of system activity to find out their cause.