Abends
There are abends for each of the three types of storage problems:
- Common storage
- Common storage shortages typically result in the following abends:
- ABEND878 RC04 or RC08
- ABEND80A RC04 or RC08
- ABEND4C5 rsn xxxx2500
For common storage problems, determine which jobs or address spaces are using an excessive amount of storage. To determine the users of common storage, enable common storage tracking (CSA Tracker). For information about how to activate and review data provided by common storage tracking, see z/OS MVS Initialization and Tuning Guide. The storage totals for TCP/IP in the CSA tracker report does not reflect all the storage in use by TCP/IP. A number of TCP/IP getmain transactions are issued with the owner as SYSTEM. This storage is reported as OWNER = SYSTEM, and not OWNER = TCP/IP.
Contact the IBM® Support Center for the owner of the storage that you think is causing the problem. See Collecting documentation to submit to the IBM Support Center for more information.
- Private storage
- Private storage shortages typically result in the following abends:
- ABEND878 RC0C or RC10
- ABEND80A RC0C or RC10
If the problem is with TCP/IP private storage, submit a problem record with the IBM TCP/IP support team for dump analysis. See Collecting documentation to submit to the IBM Support Center for more information.
- CSM storage
- For CSM storage problems, review the output from any monitoring
you have been doing for CSM storage usage. Determine the largest
users of the CSM ECSA and dataspace pools (4k, 16k, 32, 60k and 180k).
See z/OS Communications Server: SNA Operation for additional information.
Contact the IBM Support Center for the owner of the CSM storage that you think is being used in excess. See Collecting documentation to submit to the IBM Support Center for more information.
If you have not been tracking CSM storage utilization, see Monitoring storage utilization to determine how to monitor this storage for use in problem diagnosis.