U4088 (X'FF8')

Explanation

A storage condition occurred during the processing of a storage condition. The reason code indicates the request type.
Reason code
Explanation
X'5B' (91)
Stack pointer corrupted at location 1.
X'5C' (92)
Stack pointer corrupted at location 2.
X'5D' (93)
Stack pointer corrupted at location 3.
X'5E' (94)
Stack pointer corrupted at location 4.
X'5F' (95)
Stack pointer corrupted at location 5.
X'60' (96)
Stack guard field has been modified unexpectedly; stack frame may be corrupted.
X'61' (97)
DSA not found in stack
X'62' (98)
Previous NAB not in stack
X'63' (99)
Stack segment owning the next-available-byte (NAB) could not be found or a DSA backchain pointer did not contain a valid 31-bit addressable address. A storage overlay problem has probably occurred.DSA backchain pointers must contain valid addresses that can be accessed as is while in 31-bit addressing mode. For instance, a 24-bit address that was obtained by using the BAL or BALR assembler instruction will contain the ILC, CC, and Program Mask in the uppermost byte of this address, thus making it an invalid address in 31-bit mode.
X'64'–X'6C' (10x)
First free storage request terminated with return code x.
X'6E'–X'74' (110 – 116)
Debug Tool storage manager control blocks corrupted.
X'75' (117)
During a stack overflow on the Down stack, the stack pointer (register 4) was not within the current Down stack segment.
X'76' (118)
The system service IARVSERV was invoked with the CHANGEACCESS,TARGET_ VIEW=HIDDEN options to create a guard page for a Down stack segment. The service returned a nonzero return code. The reason code returned by the IARVSERV service is loaded into register 3 before the abend is issued.
X'77' (119)
During a stack overflow on the Down stack, the entry point of the routine that caused the overflow could not be found or a program check occurred while attempting to access data from the routine's entry point or PPAs.
X'78' (120)
The Get Next Available Byte service (CEEVGTUN) was invoked when the stack direction was down.
X'79' (121)
The storage size requested on a stack overflow is invalid (for example negative or too big).
X'7A' (122)
An invalid stack segment was detected during stack increment processing.
X'7B' (123)
An invalid stack segment header was detected during stack increment processing.
X'C8'–X'D8' (20x)
Second free storage request terminated with return code x.
X'12C' (300)
A call to CEEVFSTR failed
X'190' (400)
There is not enough storage to initialize the MEMCHECK vhm tool.
X'191' (401)
There is no more storage to keep the MEMCHECK vhm tool working.
X'3E8'–X'3F8' (100x)
Get storage request for stack storage terminated with return code x. A reserve stack segment was not available or the reserve stack segment was already in use, so the out of storage condition CEE0PD (message CEE0813S) could not be signalled.
X'400' (1024)
An out-of-storage condition has occurred with no reserve stack allocated.
X'800' (2048)
An internal service was invoked to change the active stack to the alternate signal stack. The service returned a nonzero return code.
X'801' (2049)
The active stack was the alternate signal stack or a user context stack. While changing the active stack, one of the following occurred:
  • The system service IARV64 was invoked with the REQUEST=CHANGEGUARD, CONVERT=FROMGUARD options to remove the guard page from the alternate signal stack or a user context stack. The service returned a nonzero return code.
  • An internal service was invoked to change the active stack. The service returned a nonzero return code.
X'802' (2050)
Automatic expansion of the user stack failed. Either MEMLIMIT was exceeded or storage for a work area could not be obtained.
X'803' (2051)
The reserve stack is full. Automatic expansion is not available for this stack.
X'804' (2052)
The alternate signal stack or a user context stack supplied by the application is full. Automatic expansion is not available for these stacks.
X'805' (2053)
An internal service was invoked to change the active stack to the reserve stack. The service returned a nonzero return code.
X'806' (2054)
The active stack was the reserve stack. An internal service was invoked to change the active stack. The service returned a nonzero return code.
X'807' (2055)
Automatic expansion of the user stack failed. The stack has already been expanded to its maximum size.
X'808' (2056)
The system service IARV64 was invoked with the REQUEST=CHANGEGUARD, CONVERT=TOGUARD options to create a guard page for the alternate signal stack or a user context stack. The service returned a nonzero return code.
X'809' (2057)
An application-managed stack supplied by the application is full. Automatic expansion is not available for these stacks.
X'80A' (2058)
The system service IARV64 was invoked with the REQUEST=CHANGEGUARD, CONVERT=TOGUARD options to create a guard page for a user context stack. The service returned a nonzero return code.
X'80B' (2059)
The system service IARV64 was invoked with the REQUEST=CHANGEGUARD, CONVERT=FROMGUARD options to remove the guard page from a user context stack. The service returned a nonzero return code.
X'80C' (2060)
An internal service was invoked to change the active stack. The service returned a nonzero return code.
X'BB8'–X'BC8' (300x)
Get storage request for stack storage terminated with return code x. The out of storage condition CEE0PD (message CEE0813S) has already been signalled to allow user condition handlers to free storage.
nnn
Critical condition nnn was signaled, but CEESGL returned control to the signaller. The signaller does not support a retry of the operation, so the module terminated.

System action

Enclave terminated.

Programmer response

For reason codes 91–20x, probable internal malfunction or storage corruption. For reason code 96, check if the program has any stack buffer overflow issues. For code 1001 or 1004, increase the region size or check for infinite recursion. For reason code 1024, increase the region size or request a reserve stack. Use the STORAGE runtime option to get more information about the environment leading up to the out-of-storage condition or allow a user handler to get control and respond to the condition.