Rational Developer for System z
Enterprise PL/I for z/OS, Version 3.8, Messages and Codes Manual

Code Generation Messages (5000-5999)

IBM5001
INTERNAL COMPILER ERROR: text
Explanation:

An internal compiler error occurred during compilation.

Contact your Service Representative.

IBM5002
Virtual storage exceeded.
Explanation:

The compiler ran out of memory trying to compile the file. This sometimes happens with large files or programs with large functions. Note that very large programs limit the amount of optimization that can be done.

Shut down any large processes that are running, ensure your swap path is large enough, turn off optimization, and redefine your virtual storage to a larger size. You can also divide the file into several small sections or shorten the function.

IBM5003
text
Explanation:

General error message.

IBM5031
Unable to open file filename.
Explanation:

The compiler could not open the specified file.

Ensure the file name is correct. Ensure that the correct file is specified. If the file is located on a LAN drive, ensure the LAN is working properly. Also, the file may be locked by another process or access may be denied because of insufficient permission.

IBM5032
An error occurred while reading file filename.
Explanation:

The compiler detected an error while reading from the specified file.

Ensure that the correct file is being read and has not been damaged. If the file is located on a LAN drive, ensure the LAN is working properly.

IBM5033
An error occurred while writing to file filename.
Explanation:

The compiler detected an error while writing to the specified file.

Ensure that the correct file is specified. If the file is located on a LAN drive, ensure the LAN is working properly.

IBM5034
Read-only pointer initialization of dynamically allocated object name is not valid.
Explanation:

The value of a read-only pointer must be known at compile time; a pointer cannot be read-only and point to a dynamically allocated object at the same time because the address of the pointee is known at run time only.

Modify the code so that the pointer is initialized with a read-only value or make the pointer read-write.

IBM5051
Function function-name exceeds size limit.
Explanation:

The ACU for the function exceeds the LIMIT specified in the INLINE suboption.

Increase LIMIT if feasible to do so.

IBM5052
Function function-name is (or grows) too large to be inlined.
Explanation:

A function is too large to be inlined into another function.

IBM5053
Some calls to function function-name cannot be inlined.
Explanation:

At least one call is either directly recursive, or the wrong number of parameters were specified.

Check all calls to the function specified and make that number of parameters match the function definition.

IBM5054
Automatic storage for function function-name increased to over value.
Explanation:

The size of automatic storage for function increased by at least 4 KB due to inlining.

Avoid inlining of functions which have large automatic storage.

IBM5055
Parameter area overflow while compiling function-name. Parameter area size exceeds the allowable limit of value.
Explanation:

The parameter area for a function resides in the first 4K of automatic storage for that function. This message indicates that the parameter area cannot fit into 4K.

Reduce the size of the parameter area by passing fewer parameters or by passing the address of a large structure rather than the structure itself.

IBM5057
name section size cannot exceed 16777215 bytes. Total section size is value bytes.
Explanation:

A Data or Code section cannot exceed 16M in size.

Partition input source files into multiple source files which can be compiled separately.

IBM5101
Maximum spill size of value is exceeded in function function-name.
Explanation:

Spill size is the size of the spill area. Spill area is the storage allocated if the number of machine registers is not sufficient for program translation.

Reduce the complexity of the program and recompile.

IBM5102
Spill size for function function-name is not sufficient. Recompile specifying option SPILL(n) where lower-limit < n <= upper-limit.
Explanation:

Spill size is the size of the spill area. Spill area is the storage allocated if the number of machine registers is not sufficient for program translation.

Recompile using the SPILL(n) option lower-limit < n <= upper-limit or with a different OPT level.

IBM5103
Internal error while compiling function function-name text.
Explanation:

An internal compiler error occurred during compilation.

Contact your Service Representative or compile with a different OPT level.

IBM5104
Internal error while compiling function function-name text. Compilation terminated.
Explanation:

An internal compiler error of high severity has occurred.

Contact your Service Representative. Be prepared to quote the text of this message.

IBM5105
Constant table overflow compiling function function-name. Compilation terminated.
Explanation:

The constant table is the table that stores all the integer and floating point constants.

Reduce the number of constants in the program and recompile.

IBM5106
Instruction in function function-name on line value is too complex. Compilation terminated.
Explanation:

The specified instruction is too complex to be optimized.

Reduce the complexity of the instruction and recompile, or recompile with a different OPT level.

IBM5107
Program too complex in function function-name.
Explanation:

The specified function is too complex to be optimized.

Reduce the complexity of the program and recompile, or recompile with a different OPT level.

IBM5108
Expression too complex in function function-name. Some optimizations not performed.
Explanation:

The specified expression is too complex to be optimized.

Reduce the complexity of the expression or compile with a different OPT level.

IBM5109
Infinite loop detected in function function-name. Program may not stop.
Explanation:

A loop which may be infinite has been detected in the given function, and your code may need to be changed. However, sometimes the compiler will issue this message when your code is OK. For example, if the loop is exited via a GOTO out of an ON-unit, the compiler may issue this message although you would not need to change your code.

Recode the loop so that it will end.

IBM5110
Loop too complex in function function-name. Some optimizations not performed.
Explanation:

The specified loop is too complex to be optimized.

No action is required.

IBM5111
Division by zero detected in function function-name. Runtime exception may occur.
Explanation:

A division by zero has been detected in the given function.

Recode the expression to eliminate the divide by zero.

IBM5112
Exponent is non-positive with zero as base in function function-name. Runtime exception may occur.
Explanation:

This is a possible floating-point divide by zero.

Recode the expression to eliminate the divide by zero.

IBM5113
Unsigned division by zero detected in function function-name. Runtime exception may occur.
Explanation:

A division by zero has been detected in the given function.

Recode the expression to eliminate the divide by zero.

IBM5114
Internal error while compiling function function-name text.
Explanation:

An internal compiler error of low severity has occurred.

Contact your Service Representative or compile with a different OPT level.

IBM5115
Control flow too complex in function function-name; number of basic blocks or edges exceeds value.
Explanation:

Basic blocks are segments of executable code without control flow. Edges are the possible paths of control flow between basic blocks.

Reduce the complexity of the program and recompile.

IBM5116
Too many expressions in function function-name; number of symbolic registers exceeds value.
Explanation:

Symbolic registers are the internal representation of the results of computations.

Reduce the complexity of the program and recompile.

IBM5117
Too many expressions in function function-name; number of computation table entries exceeds value.
Explanation:

The computation table contains all instructions generated in the translation of a program.

Reduce the complexity of the program and recompile.

IBM5118
Too many instructions in function function-name; number of procedure list entries exceeds value.
Explanation:

The procedure list is the list of all instructions generated by the translation of each subprogram.

Reduce the complexity of the program and recompile.

IBM5119
Number of labels in function function-name exceeds value.
Explanation:

Labels are used whenever the execution path of the program could change; for example: if statements, switch statements, loops or conditional expressions.

Reduce the complexity of the program and recompile.

IBM5120
Too many symbols in function function-name; number of dictionary entries exceeds value.
Explanation:

Dictionary entries are used for variables, aggregate members, string literals, pointer dereferences, function names and internal compiler symbols.

Compile the program at a lower level of optimization or simplify the program by reducing the number of variables or expressions.

IBM5121
Program is too complex in function function-name. Specify MAXMEM option value greater than value.
Explanation:

Some optimizations not performed.

Recompile specifying option MAXMEM with the suggested value for additional optimization.

IBM5122
Parameter area overflow while compiling name. Parameter area size exceeds value.
Explanation:

The parameter area is used to pass parameters when calling functions. Its size depends on the number of reference parameters, the number and size of value parameters, and on the linkage used.

Reduce the size of the parameter area by passing fewer parameters or by passing the address of a large structure rather than the structure itself.

IBM5123
Spill size for function function-name is exceeded. Recompile specifying option SPILL(n) where lower-limit < n <= upper-limit for faster spill code.
Explanation:

Spill size is the reserved size of the primary spill area. Spill area is the storage allocated if the number of machine registers is not sufficient for program translation.

Recompile using the SPILL(n) option with lower-limit < n <= upper-limit for improved spill code generation.

IBM5130
An error occurred while opening file filename.
Explanation:

The compiler could not open the specified file.

Ensure the file name is correct. Ensure that the correct file is being opened and has not been damaged. If the file is located on a LAN drive, ensure the LAN is working properly. Also, the file may be locked by another process or access may be denied because of insufficient permission.

IBM5131
An error occurred while writing file filename.
Explanation:

The compiler could not read from the specified file.

Ensure the file name is correct. Ensure that the correct file is being written to and has not been damaged. If the file is located on a LAN drive, ensure the LAN is working properly. Also, the file may be locked by another process or access may be denied because of insufficient permission.

IBM5132
An error occurred while closing file filename.
Explanation:

The compiler could not write to the specified file.

Ensure the file name is correct. Ensure that the correct file is being closed and has not been damaged. If the file is located on a LAN drive, ensure the LAN is working properly. Also, the file may be locked by another process or access may be denied because of insufficient permission.

IBM5141
Automatic area for function-name is too large
Explanation:

Automatic data resides in the stack; the stack size is limited by the target machine addressabilty.

Avoid large structures and large arrays as local variables; try using dynamically allocated data. Alternatively, try to break down the procedure into several smaller procedures.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)