How storage conditions impact new tasks
CICS® attempts to alleviate storage stress conditions by releasing programs with no current user, and by not attaching new tasks.
If these actions fail to eliminate storage stress, or if the short-on-storage (SOS) condition is caused by a suspended GETMAIN, one or more of the following messages is sent to the console:
DFHSM0131 applid CICS is under stress (short on storage below 16MB)
DFHSM0133 applid CICS is under stress (short on storage above 16MB)
DFHSM0606 applid The amount of MVS above the bar storage available to CICS is critically low
If you do not observe the SOS messages, you can find out how many times CICS became SOS from the storage manager statistics (the "Times went short on storage" statistic). You can also get this information from the storage manager domain DSA summary in a formatted system dump.
For more information about short-on-storage conditions, see Short-on-storage conditions in dynamic storage areas.
- storage getting short
- storage critical
It is likely that "storage getting short" and "storage critical" conditions occur many times for every occasion that the SOS condition is reached. To see how often these points are reached, select level-2 tracing for the dispatcher domain and look out for trace point IDs DS 0038 ("storage getting short") and DS 0039 ("storage critical"). Trace point DS 0040 shows that storage is OK.
| State of storage | Effects on user tasks |
|---|---|
| Storage getting short | Priority of new user tasks reduced a little |
| Storage critical | Priority of new user tasks reduced considerably |