30D

Explanation
End of memory (EOM) processing has detected that
an EOM resource manager has been inactive (not dispatched) for at
least 4 minutes.  That EOM resource manager is considered to have
failed and receives this abend.  
The hexadecimal reason codes
are:Code
Explanation
00
The failing resource manager receives this reason code.
04
This reason code is used internally during the detection process.
This reason code may be seen in the LOGREC record that the system
records for this abend.

System action
The system takes a synchronous SVCDUMP to capture
the situation, then issues this abend.  The abend is retriable.  If
the EOM resource manager's recovery fails to retry, EOM processing
will continue with the next EOM resource manager.

System programmer response
The title of the SVCDUMP will begin
with "END OF MEMORY RESOURCE MANAGER HANG DETECTED:", and will contain
a TCB address as well as the name or address of the last EOM resource
manager that was given control.  The owner of that resource manager
should examine the indicated TCB (which is in ASID 1) to determine
why it was not progressing and correct the situation that caused the
resource manager to fail in this way.Note: Since the SVCDUMP is taken
before ABEND30D is issued (to provide a more clear picture of the
problem), this abend will not be seen under the failing TCB in the
dump. It may be seen under the detecting TCB (with reason code 04)
and should be ignored there.

Programmer response
None.

Source
Recovery Termination Manager (RTM)