A78

Explanation
An error occurred when the system tried to process
an RU or RC form of the FREEMAIN macro or the STORAGE RELEASE macro.
A reason code in the SDWACRC field of the system diagnostic work area
(SDWA) explains the error: Code
Explanation
04
The system queue area (SQA) storage to be freed overlaps free
storage.
08
The common service area (CSA) storage to be freed overlaps free
storage.
0C
The local system queue area (LSQA) storage to be freed overlaps
free storage.
10
The private area storage to be freed overlaps free storage.
14
Part of the CSA to be freed is fixed.
18
Part of the private area to be freed is fixed.
1C
The private area to be freed is associated with a data-in-virtual
object.
20
The private area to be freed has been specified on the IARSUBSP
IDENTIFY request, and is eligible to be assigned to a subspace.
24
The task or SRB routine tried to free either SQA storage that
overlaps free storage or SQA storage that was obtained by more than
one request.
28
The task or SRB routine tried to free either CSA storage that
overlaps free storage or CSA storage that was obtained by more than
one request.
2C
Part of the SQA area to be freed is fixed.
30
Part of the LSQA area to be freed is fixed.

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

Programmer response
Do the following: For reason code X'1C', ensure that the program issued
a DIV UNIDENTIFY request before any FREEMAIN or STORAGE RELEASE request.
For reason code X'24' or X'28', ensure that
the start address, length and subpool specified on the FREEMAIN or
STORAGE RELEASE macro do not contain errors.
Ensure that the FREEMAIN or STORAGE RELEASE operands do not specify
a different subpool and/or key than the subpool or key of the storage
you are trying to free.
Ensure that the task control block (TCB) specified on the FREEMAIN
or STORAGE RELEASE request is the same one specified on the corresponding
GETMAIN or STORAGE OBTAIN request.
If a caller running in supervisor state and key 0 made the original
GETMAIN or STORAGE OBTAIN request, ensure that the corresponding FREEMAIN
or STORAGE RELEASE request is also issued in supervisor state and
key 0. If a caller in supervisor state and key 0 requests storage
in subpool 0 or 250, the system satisfies this request with storage
from a different subpool. This situation is described in z/OS MVS Diagnosis: Reference. 

If the storage is eligible to be assigned to a subspace, make
the storage ineligible by specifying the storage range on an IARSUBSP
UNIDENTIFY request before attempting to release the storage.
Check for program errors that incorrectly modify the FREEMAIN
or STORAGE RELEASE macro expansion.

Source
Virtual storage manager (VSM)