When common system abends occur

There are abends or performance problems not caused by failures in DFSMSrmm. For example, your batch job might end abnormally because of system errors beyond your control. Abends can also result from using inadequate or incorrect storage parameters. See your system programmer for assistance in diagnosing these errors.

This topic lists abends you might encounter when running DFSMSrmm, and suggests ways of correcting the problem. Not every possible problem can be listed, but the list includes those most commonly reported to IBM® personnel.

These are common system abend codes that might appear when abends result from errors in storage parameters.

106: Sufficient storage was unavailable to load a module. Ensure that the value for REGION is sufficient.
804: The amount of storage requested exceeded that available. Ensure that the value for REGION is sufficient.
878: The amount of storage requested exceeded that available. Ensure that the value for REGION is sufficient.
80A: This abend occurs when a DFSMSrmm job requires more storage than has been allocated. Ensure that the value for REGION is sufficient.
D37: An output data set is specified with insufficient primary SPACE allocation and no secondary allocation. If this abend occurs during inventory management for the temporary data set allocated with the ddname SRTINOUT, the DFSMSrmm control data set control record might be incorrect. Run the EDGUTIL utility with the VERIFY parameter to check the consistency of the control data set and control record. Increase the primary allocation or include a value for secondary allocation.
E37: An output data set is allocated on a primary volume that has either insufficient storage or excessive fragmentation, and no secondary volume is specified. Allocate the data set on a volume with more space or perform space management on the primary volume.