878

Explanation
The error occurred when the system was trying to
do one of the following: Satisfy a request made through the STORAGE macro
Process an RU or VRU form of the GETMAIN macro
Process an RU form of the FREEMAIN macro

A reason code in the SDWACRC field of the system diagnostic
work area (SDWA) explains the error: Code
Explanation
04
There is not enough virtual system queue area (SQA) storage available
to satisfy the request.
08
There is not enough virtual common service area (CSA) storage
available to satisfy the request.
0C
There is not enough virtual local system queue area (LSQA) storage
available to satisfy the request.
10
There is not enough virtual private area storage available to
satisfy the request. This is due to one of the following: A program is requesting virtual storage, but not subsequently
freeing the storage.
The region size specified is too small.
An installation exit is requesting virtual storage from a V=R
region before initialization of the region has completed.

14
A negative amount of storage was specified on a GETMAIN macro. Note: If
this error is detected, the calling program abnormally ends even though
RC, EC, LC, or VC is specified for GETMAIN, or COND=YES is specified
for STORAGE.

18
A negative amount of storage was specified on the FREEMAIN or
STORAGE macro. Note: If this error is detected, the calling program
abnormally ends even though RC, EC, LC, or VC is specified for FREEMAIN,
or COND=YES is specified for STORAGE.

1C
During request processing, the system tried to get LSQA virtual
storage for virtual storage management's (VSM) cell pool.  There was
not enough LSQA virtual storage available.
20
There is not enough virtual storage in the LSQA to build a new
address queue anchor table (AQAT) stack.
24
A GETMAIN or STORAGE OBTAIN request with the LOC=EXPLICIT keyword
specified failed for one of the following reasons: Part of the requested area was already allocated.
Storage was already allocated in the same page as this request,
but one of the following characteristics of the storage was different: The subpool
The key
Central storage backing

28
A GETMAIN or STORAGE OBTAIN request with the LOC=EXPLICIT keyword
specified failed because part of the requested area exceeds the bounds
of the region.

System action
The system issues message IEA705I. The system
abnormally ends the current task.

Programmer response
A complete dump is necessary to diagnose
this out of storage condition.  If no dump was produced, SLIPs should
be set to obtain a dump on problem recurrence. Further debugging information
may be found in Informational APAR II05506. An abend 80A can cause
this same condition, so both SLIPs should be set as follows:   SLIP SET,COMP=878,A=SVCD,SDATA=(ALLNUC,
   PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END

  SLIP SET,COMP=80A,A=SVCD,SDATA=(ALLNUC,
   PSA,SQA,CSA,LPA,TRT,LSQA,RGN),END
 Also, depending on
the reason code, do one of the following: 10
Try increasing the region size specified in the region parameter
on the JOB or EXEC statement in the JCL for the job. However, if the
cause of the problem is actually that a program is requesting virtual
storage and not freeing it, the abend will recur when the program
uses the virtual storage in the larger region.
24
Ensure that the calling program specifies the following correctly: The storage address on the INADDR keyword.
The length on the LENGTH keyword for the STORAGE macro or the
LV keyword for the GETMAIN macro.
The desired subpool or key.
The target address space for the STORAGE macro.
The TCB address for the STORAGE macro.

 Make sure also that the area of storage you are requesting is
completely free. If part of the area requested is in a page that is
already allocated, make sure that the central storage backing specified
on the LOC=EXPLICIT keyword matches that of the allocated storage.
28
Ensure that the calling program specifies the following correctly: The storage address on the INADDR keyword.
The length on the LENGTH keyword for the STORAGE macro or the
LV keyword for the GETMAIN macro. Make sure also that the calling
program correctly specifies the value on the JCL REGION keyword. If
the JCL REGION value is not large enough for the requested storage
area, increase the size of the JCL REGION and resubmit the job.

04-0C, 14-20
Check for program errors that incorrectly modify the macro expansion
and correct them. If necessary, change the program to request less
virtual storage.

Source
Virtual storage management (VSM)