Explanation
A system error, uncorrectable machine error, or
error that cannot be determined, occurred when the system tried to
process an R form of the GETMAIN or FREEMAIN macro. A reason code
in the SDWACRC field of the system diagnostic work area (SDWA) explains
the error:
Note: Some VSM return codes may be a half-word in length.
In these cases, the high-order byte is the module id of the issuing
module, and the low-order byte is the return code.
- Module ID
- Module Name
- 1
- IGGVVSMRT
- 3
- IGVVSM24
- 4
- IGVVSM31
- 6
- IGVGSQA
- 7
- IGVFSQA
- A
- IGVGLSQA
- B
- IGVFLSQA
- C
- IGVGAPVT
- E
- IGVFSP
- 44
- IGVVSMRF
- Code
- Explanation
- 01
- While processing the FREEMAIN request, the system tried to release
central storage backing global or local system queue area (SQA or
LSQA) storage. A program page fixed the virtual storage. However,
it is a basic property of the system that SQA and LSQA storage is
page fixed.
- 02
- While processing a subpool FREEMAIN of a local system queue area
subpool, a service routine was called to free storage described by
an allocated element (AE). The service routine returned a return
code indicating that the storage is not described by an AE.
- 04
- Status information indicates that the system has obtained a global
lock in support of the FREEMAIN request. However, when the system
attempted to release the lock, the release request failed.
- 08
- A GETMAIN storage management service routine returned an incorrect
return code to the virtual storage manager (VSM) interface module.
- 09
- While getting or freeing storage in a local or global system queue
area subpool, the service routine that builds double free elements
(DFE) tried to place virtual storage on the DFE queue, but could not
do so because the storage was described by another DFE already on
the queue.
- 0C
- A FREEMAIN storage management service routine returned an incorrect
return code to the virtual storage manager (VSM) interface module.
- 10
- While in recovery processing, the system detected a condition
that is normally considered a user error, such as an error in the
parameter list. However, the error is most likely not a user error
because recovery processing is in control.
System action
The system writes a logrec data set error record.
The system continues processing.
System programmer response
Search problem reporting data bases
for a fix for the problem. If no fix exists, contact the IBM® Support Center.
Programmer response
Run the job again. If the error recurs,
contact the system programmer.
Source
Virtual storage manager (VSM)