You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there are variable-length data items (e.g. OCCURS ~ DEPENDING ON) in WORKING-STORAGE SECTION (not at the end, but in the middle), we can compile source file with complex-odo: yes in configuration file.
But, for example, the following cannot compile.
WORKING-STORAGE SECTION.
01 A.
02 B PIC 9(8) BINARY.
02FILLER01OCCURS227DEPENDINGON B
PIC X(1).
02 C PIC S9(004) COMP.
The generated Java source code appears to contain C source code as is (b_C__A + 4 + 227.fillBytes(0, 2);).
In version 1.0.7, this way of writing was not a problem, but in latest version, it seems to cause a runtime error.
By writing b_PPLEN__MY_REC.fillBytes(0, 2);, the runtime error was resolved.
I don't know if this is the ideal way.
If there are variable-length data items (e.g.
OCCURS ~ DEPENDING ON
) inWORKING-STORAGE SECTION
(not at the end, but in the middle), we can compile source file withcomplex-odo: yes
in configuration file.But, for example, the following cannot compile.
The generated Java source code appears to contain C source code as is (
b_C__A + 4 + 227.fillBytes(0, 2);
).This should be
b_C__A.getSubDataStorage(4 + 227).fillBytes(0, 2);
.The text was updated successfully, but these errors were encountered: