C/C++ Programmer's Guide (G06.27+, H06.08+, J06.03+)

Effect
The CRE terminates the program.
Recovery
Use a compiler and run-time library that are compatible. You might need to consult your system
administrator.
Ensure that the application is linked to the correct libraries, in the correct order, for the functions
or features used. For example, if you are using the version of the getgrent_r() function that
uses three parameters, ensure that you specify linking to the Standard POSIX Threads library
(ZSPTDLL) before you specify linking to the public library ZSECDLL.
Heap-Management Messages
The CRE or run-time libraries report the messages in this subsection if they detect an error while
accessing the heap.
30
Unknown heap error
Cause
A heap-management routine was called with an invalid error number.
Effect
The CRE terminates the program.
Recovery
Refer to the reference manual that corresponds to the language in which the routine that requests
heap space is written. You might need to consult your system administrator.
31
Cannot obtain data space
Cause
Your program, or the run-time library for one of the modules in your program, requested more
space on the heap than is currently available.
Effect
Program behavior is language and application dependent.
Recovery
Refer to the reference manual that corresponds to the language in which the routine that requests
heap space is written. You might need to consult your system administrator.
32
Invalid heap or heap control block Process heap size is 0
Cause
The CRE or a run-time library found invalid data in the user heap or in the heap control block.
Your program might be writing information over the heap or heap control block. An invalid
pointer or indexing operation could cause this error.
“Process heap size is 0” appears when your program or a run-time library requested space, but
the process has no user heap.
Effect
Program behavior is language and application dependent.
370 Run-Time Messages