Common system abends related to storage

Table 1 covers common system abend codes that might appear when abends result from errors in storage parameters. The items are listed by system abend code. For details on DFSORT’s use of storage and storage parameters, see z/OS DFSORT Installation and Customization and z/OS DFSORT Application Programming Guide.

Table 1. Common System Abends Related to Storage
Abend Code	Problem
106	There was not sufficient storage to load a module. Ensure that the values for REGION, MAINSIZE, SIZE, RESALL or RESINV are sufficient.
804	The amount of storage requested exceeded that available. Ensure that the values for REGION, MAINSIZE, SIZE, RESALL or RESINV are sufficient.
878	User exits required more storage than was available. Ensure that the values for each user exit size in the MODS statement and for REGION, MAINSIZE, SIZE, RESALL or RESINV are sufficient.
80A	This abend can result from the following: A DFSORT job required more storage than was available. Ensure that the values for REGION, MAINSIZE, SIZE, RESALL or RESINV are sufficient. The '-1' flag required to mark the end of an extended parameter list was missing. Include an F'-1' to mark the last item in the parameter list. The invoking program used AL3 to define addresses for DFSORT control statements. Be sure to use full 4-byte addresses to prevent DFSORT from "running off the end" while allocating storage.
D37	A SORTWK, SORTOUT, or OUTFIL data set was specified with insufficient primary space allocation and no secondary allocation. Increase the primary allocation, or include a value for secondary allocation.
E37	A SORTOUT or OUTFIL data set was allocated on a primary volume that had either insufficient storage or excessive fragmentation, and no secondary volume was specified. Specify more than one volume in the VOLSER parameter for the SORTOUT or OUTFIL data set or compress the volume to allow it to contain the full 16 extents.