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.

The dispatcher recognizes two other conditions on the approach to an SOS condition:
  • storage getting short
  • storage critical
These two conditions affect the chance of new tasks getting a first dispatch. From the point when storage gets short, through to when storage gets critical and up to the SOS condition, the priorities of new user tasks are reduced in proportion to the severity of the condition. However, this is not true if the PRTYAGE system initialization parameter is set to 0. At first, you are not likely to notice the effect, but as the "storage critical" condition is approached, new tasks might typically be delayed by up to a second before they are dispatched for the first time.

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.

The following table summarizes the effects of storage conditions on task priorities:
Table 1. How storage conditions affect new tasks getting started
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


dfhs1c00183.html | Timestamp icon Last updated: Monday, 5 June 2017