Detecting storage violation

CICS® can detect storage violations when:

A storage violation can occur in two basic situations:

  1. 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.
  2. 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.

Related tasks
Identifying CICS constraints
Observing response times
Identifying storage stress
Identifying paging problems
Dealing with limit conditions
Identifying performance constraints
Dealing with resource contention
[[ Contents Previous Page | Next Page Index ]]