Troubleshooting
Problem
A System 00F4 abnormal termination (ABEND) has a reason code in the general-purpose register 0, that, when deciphered, provide additional information to the cause of the failure. A group of these codes indicate the occurrence of an out of storage condition. Knowing the reason for the ABEND might assist in determining what actions have to be taken to remedy the situation.
Symptom
Many ABENDs, including but not limited to S0F4 ABENDS, have an underlying reason code in the general-purpose register 0 that, when, deciphered, indicate the occurrence of an 'out of storage' condition. By, knowing the underlying cause of the abend the user is better able to take steps to remedy the situation. These ABENDs can be reported by various means:
Although this item is described under the PDSE component, its scope is not limited to the PDSE component. A number of other DFSMS and MVS system components use the PDSE Virtual Storage Management (VSM) subcomponent to implement VSM cell pool management. Included in these components are VSAM RLS, VSAM TFS, DFM, HFS, and CMM.
.
Resolution:
DFSMS Reason codes in are the last two bytes of the word as seen in GPR0 at ABEND. The first two bytes identify a subcomponent and module ID and the last two bytes are a specific reason. It is important to note that different modules might issue the write the same two byte reason code. Therefore, the important concept is to know what the last two bytes mean.
The most common out of space reason codes and their meaning are:
2504C002 ECSA storage exhausted.
2504C003 User private storage exhausted.
2504C004 DREFED AUTODATA storage exhausted. Usually ELSQA (high private.)
xxxxC005 No DASD space available.
For all but the last reason code, a GETMAIN failure occurs.
- SYSLOG symptom dump entries
- SYSTEM dumps
- EREP LOGREC SOFTWARE or SYMPTOM records.
Although this item is described under the PDSE component, its scope is not limited to the PDSE component. A number of other DFSMS and MVS system components use the PDSE Virtual Storage Management (VSM) subcomponent to implement VSM cell pool management. Included in these components are VSAM RLS, VSAM TFS, DFM, HFS, and CMM.
.
Resolution:
DFSMS Reason codes in are the last two bytes of the word as seen in GPR0 at ABEND. The first two bytes identify a subcomponent and module ID and the last two bytes are a specific reason. It is important to note that different modules might issue the write the same two byte reason code. Therefore, the important concept is to know what the last two bytes mean.
The most common out of space reason codes and their meaning are:
2504C002 ECSA storage exhausted.
2504C003 User private storage exhausted.
2504C004 DREFED AUTODATA storage exhausted. Usually ELSQA (high private.)
xxxxC005 No DASD space available.
For all but the last reason code, a GETMAIN failure occurs.
[{"Product":{"code":"SWG90","label":"z\/OS"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"5695DF115 - DFSMS\/MVS PDSE AND FAMS","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"2.1;2.2;2.3","Edition":"","Line of Business":{"code":"LOB56","label":"Z HW"}}]
Was this topic helpful?
Document Information
Modified date:
03 September 2021
UID
isg3T1010623