Compile failure when compiling RDMLX objects & WAMs with error MCH3203 in joblogs
|Product/Release:||LANSA for iSeries V11.0|
|Abstract:||Compiles on iSeries of objects that generate C can fail with error MCH3203 in the joblog|
|Submitted By:||LANSA Technical Support|
Compilations on iSeries can fail with the following error in the joblog:
MCH3203 Escape 60 10/04/06 14:13:04.283127 VOXALIAS 004C1C QBNCRTMD QSYS *STMT
From user . . . . . . . . . : O_LANSA05
To module . . . . . . . . . : QBNCRTMD
To procedure . . . . . . . : main_module
Statement . . . . . . . . . : 1038
Message . . . . : Function error in machine instruction. Internal dump
identifier (ID) .
Cause . . . . . : The machine instruction that was running failed. Time
stamp is , error code is , error class is , device number is . The error
class indicates how the damage was detected: 0000-unspecified abnormal
condition; 0002-logically invalid device sector; 0003-device failure. For
error class 0003, the device number identifies the failing device, or
contains zero if main storage failed.
Recovery . . . : Start problem analysis (ANZPRB command).
The most likely scenario to generate this error is when checking in and compiling a WAM (or other RDMLX object). The failure within the compiler may have to do with the size of the WAM in terms of the generated C. Hence, it is more likely to occur in large and complex WAMs with many webroutines.
This is caused by an IBM compiler issue which may occur when compiling some modules with optimization levels 20, 30, 40 and a fix is available via PTF.
This PTF will need to be applied to resolve the issue.
Note: If observable information has been removed from the affected object, the customer can circumvent the problem by compiling the program source code with optimization level *NONE or 10.