Joined: 03 Oct 2009 Posts: 1790 Location: Bloomington, IL
But, really trying to understand, did it abend because of the insufficient space in the system at that point of time'?
Might could be. As the entry for ICE046A in the DFSORT Messages, Codes, and Diagnosis Guide states:
DFSORT was not able to complete processing with the intermediate storage available (Hiperspace or disk work data sets). [...]
The amount of intermediate storage required can vary depending on many factors including:
•The amount of Hiperspace DFSORT is able to use at the time the sort is run
•The amount of main storage available
•The degree of randomness of the records to be sorted
•The values specified (or defaulted) for options such as DYNALOC, DYNAUTO, DYNSPC, FILSZ/SIZE, AVGRLEN, or DYNALLOC
•The amount of padding required for short records when VLSHRT is in effect.
I see that you have provided the solution for getting rid of this error message. But, per my original question, I am looking for the reason as to why it failed in the first place, as when I reran the same step with no changes, it did run fine!
I am digging to this depth because, every month end, when there is heavy processing in the system, SORT fails in one or the other job with this error message, then the solution is as simple as , restart the step with no changes and it runs fine.
Per my experience, my guesses are
1. Region parameter in the job is playing a role, due to high traffic in the system at that point of time
2. There were no sufficient volumes(space) available in the system at that point of time
You have messages in the sysout about disk work datasets. If a Sort is using disk work datasets, there is not enough "memory", in one form or another, to do the sort "in core".
Your disk work datasets are not being allocated effectively, as you are giving Sort no indication from you of the number of records and, due to the involvement of an "exit" (the Cobol program doing the Sort), Sort cannot tell from the dataset(s) as it is not even aware of what they are.
With effective allocation of disk work datasets the message will "go away". I'd think that one of the other reasons must be likely only if no disk work datasets have already been used - but that's just me thinking.
If you look through the linked-to topic, and perhaps this one, you'll find about everything that you can look up to see what affects allocation of disk work space, and other types of work space.
If you get the message again, look for other "unusual" messages in the step. It'll probably get you there.