Is fragmentation of unallocated storage causing the WRITEQ TS request to fail?
You can tell whether fragmentation of unallocated temporary storage is causing the WRITEQ TS request to fail by looking at the temporary storage summary in the dump.
The following fields in the summary are of interest should your task be
suspended on resource type TSAUX:
Number of control intervals in data set:
Number of control intervals currently in use:
Available bytes per CI:
For control intervals of 4K, the available bytes per CI figure is 4032.
If your task is attempting to a write a record that is smaller than or equal to the available bytes per CI figure (including its record header which is 28 bytes long), this means that no control interval has the required amount of contiguous space to satisfy the request.
If your task is attempting to write a record that is longer than the available
bytes per CI figure, CICS splits the record into sections of a length
equal to this figure. CICS then attempts to store each section in a completely
empty control interval, and any remaining part of the record in a control
interval with the contiguous space to accommodate it. If your task is waiting
on resource type TSAUX after having attempted to write a record longer than
the available bytes per CI figure, either of the following
has occurred:
- There are not enough available completely empty control intervals to accommodate
all the sections
(CIs in data set - CIs in use) < (record length / available bytes per CI) - No control interval has enough contiguous space to accommodate the remainder.