Investigating storage waits
If a task is waiting for a long time on any of the resource types CDSA, RDSA, SDSA, UDSA, ECDSA, ERDSA, ESDSA, ETDSA, EUDSA, GCDSA, GUDSA, or GSDSA, you can use a CICS® system dump to investigate further.
About this task
Waits on these resources occur when tasks make unconditional storage requests (SUSPEND=YES) that cannot be satisfied. For storage requests below the 16 MB line, waits can be on the CDSA, RDSA, SDSA, or UDSA. For storage requests above 16 MB but below 2 GB, waits can be on the ECDSA, ERDSA, ESDSA, ETDSA, or EUDSA. For storage requests above the bar, waits can be on the GCDSA, GUDSA, or GSDSA.
If tasks make conditional storage requests (SUSPEND=NO), tasks are not suspended on these resources. If the request cannot be satisfied, an exception response is returned.
CICS automatically attempts to relieve storage when it is under stress, for example by releasing storage occupied by programs whose current use count is 0. Also, if a task waits for storage longer than the deadlock timeout parameter specified in the installed transaction definition, the task might be automatically purged. Certain conditions prevent purging of a task, for example, a deadlock timeout value of 0, or a specification of SPURGE(NO).
- The task issued an unconditional GETMAIN request for an unreasonably large amount of storage.
- The task issued an unconditional GETMAIN request for a reasonable amount of storage, but the system has too little available. The system might be approaching a short-on-storage (SOS) condition, or the storage might be too fragmented to satisfy the request.