After the upgrade of a ISV product, one of this product's monthly job is abending with the ICE046A message. The vendor recommended adding additional Sortwk's and re-running the job. We added several Sortwks and received the same abend. It appears that the Sortwks are ignored and that Hiperspace is being used.
Are there run time options that we can use to override/change how Hiperspace is used to eliminate this abend?
Why don't you send the sysout to our DFSORT hotline, firstname.lastname@example.org and I'll take a look. We need to understand the cause of the ICE046A before we start just adding sortworks or turning off Hiperspace.
For benefit of others on the forum, after seeing the output, this was a program invoked sort which was passing the SORTDD parameter which changes the prefix for sort data sets from the normal default of SORT. That's why the SORTWKxx data sets had no impact. Instead DFSORT used dynamic allocation but the program was also passing an estimated file size that was too small and that led to the ICE046A.