07D

Explanation
The system found an error while adding or deleting
a functional recovery routine (FRR) from one of the FRR recovery stacks.
The
reason codes are as follows: Code
Explanation
00
The FRR recovery stack could not hold any more FRRs because all
of the available slots were filled.  This abend is probably caused
by an installation-provided program that issued SETFRR incorrectly
as follows: Adding FRRs without deleting them.
In a loop that includes a SETFRR macro.
Adding too many FRRs. The system only guarantees that installations
can add two FRRs.
As system services also need to add FRRs, dump processing
and LOGREC recording cannot be performed. S07D is normally followed
by an S0DC-8 abend which will contain recursive S07D SVCE entries
in the system trace.

04
The caller of SETFRR DELETE was not in a legal state to be holding
FRRs at the time that SETFRR DELETE was issued. From the time an
FRR is established until the time it is deleted, at least one of the
following things must be true: Some lock is held
The unit of work is running disabled
The unit of work is an SRB
An FRR with EUT=YES exists

System action
The system abnormally ends the unit of work that
issued the SETFRR macro. The system may write a logrec data set error
record. The unit of work may request a dump.

Operator response
If the system programmer asks for an SVC dump,
set the following SLIP trap: SLIP SET,COMP=07D,ACTION=SVCD,END
SLIP SET,COMP= 0DC,RE=8,ACTION=SVCD,END

System programmer response
Do the following: Check for the problem in all installation-provided
programs that are in protection key 0 and that issue SETFRR.  At the
time of the abend, register 14 points to the program that invoked
SETFRR.  This program is likely to have caused the problem.  
Format the dump for the abend to see the prefixed save
area (PSA) for the system on which the abend occurred.  The first
3 words in the PSASTAK field should contain the following: 00000BB8 00000DB8 00000020

If the PSASTAK field is incorrect, an overlay occurred.
 Use the following SLIP storage alteration trap to determine which
routine caused the overlay: SLIP SET,SA,RANGE=(B80,B8B),A=WAIT,END

For S07D-0, a dump cannot be taken. Trace entries similar to the
following will be found in the S0DC-8 dump which follows an S07D-0:01 014E *SVCE    D 040C2000 800003FA  00FF050C
816A2E88 8007D000
01 014E *SVCE    D 040C2000 800003FA  00FF050C
01371EC4 8007D000
01 014E *SVCE    D 040C2000 800003FA  00FF050C
816C50F8 8007D000
01 014E *SVCE    D 040C2000 800003FA  00FF050C
01371EC4 8007D000
01 014E *SVCE    D 040C2000 800003FA  00FF050C
816C50F8 8007D000
01 014E *SVCE    D 040C2000 800003FA  00FF050C
01371EC4 8007D000
01 014E *RCVY ABRT                            
         3C000304
01 014E *RCVY MEM           813305A8  840DC000
00000008 00000000
The SVCE D entries with R1=8007D000
indicate that S07D-0 has occurred. Although the FRR stack current
pointer will be reset in the S0DC-8 dump, there will be residual data
in the FRR stack which can be used to determine the FRR entries that
filled the stack.

Search problem reporting data bases for a fix for the
problem. If you suspect an overlay, include in the search argument: Program identifier: PIDS/5752SCRTM
System abend code: AB/S007D
The name of the field that is overlaid: FLDS/PSASTAK
Note: Prior to OS/390® the
program identifier to search for is PIDS/5752SC1CM. If no fix exists,
contact the IBM® Support Center.
Provide problem data collected in the previous steps.

Source
Recovery termination manager (RTM)