378

Explanation
An error when the system tried to process an RU
or VRU 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
08
System queue area (SQA) storage is not in the specified subpool.
0C
Common storage area (CSA) storage is not in the specified subpool,
or it is not in the specified key.
10
Local system queue area (LSQA) storage is not in the specified
subpool.
14
Private area storage is not in the specified subpool, is not in
the specific key or is not owned by the specified task.
18
The system could not find a private area subpool.
1C
A user has requested that storage at virtual address 0 be freed.
 This can happen if the user intended an entire subpool, but has incorrectly
specified a non-zero length with an address of 0. Zero length must
be specified on a subpool FREEMAIN or STORAGE RELEASE. Another possibility
is that the user has specified the wrong address.
20
One of the following: In the CSA, the area specified on a FREEMAIN or STORAGE RELEASE
is larger than the area specified on the original GETMAIN or STORAGE
OBTAIN.
The FREEMAIN or STORAGE RELEASE start address is not valid.

24
One of the following: In the private area, the area specified on a FREEMAIN or STORAGE
RELEASE is larger than the area specified on the original GETMAIN
or STORAGE OBTAIN.
The FREEMAIN or STORAGE RELEASE start address is not valid.

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

Programmer response
Do the following: Ensure that the FREEMAIN or STORAGE RELEASE operands A and LV
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 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 will satisfy this request with storage from a
different subpool. This situation is described in z/OS MVS Diagnosis: Reference. 

Check for program errors that incorrectly modify the FREEMAIN
or STORAGE RELEASE macro expansion.

Source
Virtual storage manager (VSM)