Text |
MCG module for given architecture is not present. |
Explanation |
The CPU clause of the MCG options indicates an architecture for which no module is available. |
Action |
Link the required module to the Natural nucleus, or use a different value for the CPU= clause. |
Text |
Memory shortage for STMT buffer - use bigger thread. |
Explanation |
The thread or address space is not large enough for the intermediate buffers required by the Natural Optimizer Compiler. |
Action |
Use a bigger thread or region. If it proves impossible to compile online, it may be necessary to compile in batch, where more memory is available to the nucleus. |
Text |
Block nesting error (compiler error). |
Explanation |
There are too many nested blocks in the program. NOC can only handle up to 128 nested blocks. A new block starts every time a FOR, REPEAT, READ, FIND, HISTOGRAM, READ WORK, DEFINE SUBROUTINE or AT statement is encountered and ends when the loop is closed or the block is terminated. |
Action |
Try to re-arrange the program so that the number of nested blocks is reduced. |
Text |
Parameter error - unknown or misspelled option. |
Explanation |
A parameter of the OPTIONS MCG= statement has not been recognized. Currently the following options are supported: ON OFF IO MIX INDX OVFLW RANGE ZD NODBG LOOPS NOSGNTR ERRDUMP PGEN TRSTMT TRGPT TRMPT TRVDT NOSRCE TREXT CPU=/370 OPTLEV= TRACELEV= LPP= (But please consult the latest NOC doc, there may be more). Parameters are separated by commas, without spaces. e.g. OPTIONS MCG=PGEN,OPTLEV=2,TRACELEV=127 |
Action |
Correct error in program. |
Text |
Memory shortage for generated code - use bigger thread. |
Explanation |
The thread, region or address space is not large enough for the buffer containing the generated code. |
Action |
Use a bigger thread or region. It may be necessary to compile in batch where more memory is available, if the program is very large. |
Text |
Assignment error (NOC error). |
Explanation |
A MOVE or ASSIGN between incompatible or unknown data types has occurred. |
Action |
This is an internal compiler error. Please set the additional NOC option ERRDUMP, recat the program, contact Software AG support and provide the dump. |
Text |
Not enough memory for trace data. |
Explanation |
There is not enough memory for the trace data. |
Action |
Use a bigger thread or region, or reduce the amount of trace information by using OPTIONS MCG=+PGEN before the specific area to be traced and OPTIONS MCG=-PGEN after. Or use TREXT option with user exit. |
Text |
GETMAIN of NOC runtime work buffer failed. |
Explanation |
This work buffer is used for the COMPRESS statement and overlapping moves using variables which are longer than 512 bytes. |
Action |
Increase the size of the Natural work pool (profile parameter WPSIZE) or, if not used, the region size. |
Text |
NOC error - Label could not be resolved (compiler error). |
Explanation |
During NOC generation, a label used to branch inside the code could not be resolved. This is an internal NOC problem. |
Action |
Contact your Natural administrator. |