CRE Programmer's Guide

Run-Time Diagnostic Messages
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
10-8
CRE Service Function Messages
list. Use a symbolic debugger appropriate for the type of code to help isolate the
problem.
16
Cause. The CRE did not have enough room to store all of the checkpoint information
required by the program.
Effect. Program behavior is language and application dependent.
Recovery. Increase the checkpoint list object’s size. See the language manual for the
routine that allocates your checkpoint list.
17
Cause. The CRE or a run-time library could not obtain heap space for all of its data.
Effect. If the request came from the CRE, it terminates the program. Otherwise,
program behavior is language and application dependent.
Recovery. You might be able to increase the amount of control space available to your
program by reducing the number of files your program has open at the same time or by
decreasing the size of buffers allocated to open files.
18
Cause. A module could not obtain sufficient extended stack space for its local data.
Effect. Program behavior is language and application dependent.
Recovery. Increase the extended stack’s size. See the language manual for the
routine that caused the extended stack overflow for details on increasing the size of the
extended stack.
20
Cause. A string, expected to be a valid file name, could not be manipulated as a
Guardian external file name.
Effect. If the file name came from the CRE, the program is terminated. Otherwise,
program behavior is language and application dependent.
Checkpoint list exhausted
Cannot obtain control space
Extended Stack Overflow
Cannot utilize filename