CICS® can detect storage violations when:
- The duplicate storage accounting area (SAA) or the initial SAA of a TIOA storage element has become corrupted.
- The leading storage check zone or the trailing storage check zone of a
user task storage has become corrupted.
A storage violation can occur in two basic situations:
- When CICS detects an error during its normal processing of a FREEMAIN request
for an individual element of a TIOA storage, and finds that the two storage
check zones of the duplicate SAA and the initial SAA are not identical.
- CICS also detects user violations involving user task storage by checking
the storage check zones of an element of user task storage following a FREEMAIN
command.
When a storage violation is detected, an exception trace entry is made
in the internal trace table. A message (DFHSM0102) is issued and a CICS system dump
follows if the dump option is switched on.
Storage violations can be reduced considerably if CICS has storage
protection, and transaction isolation, enabled.
See the CICS Problem Determination Guide for further information about diagnosing
and dealing with storage violations.
[[ Contents Previous Page | Next Page Index ]]