Simon Sobisch

That's a bug in the code - only the caller may define BY CONTENT (while the callee would use BY REFERENCE as a counter-side). This is all in the same area of the code and will be fixed together. I can confirm that the syntax diagram is the one you've posted above (with WITH ... LINKAGE being dialect specific and only be usable when the internal or standard-compliant manually defined call-convention mnemonic-name is not used),

The USING clause needs to be adjusted - only BY REFERENCE (default) or BY VALUE, only identifier (with identifier being a level 01/77 data-item in LINKAGE SECTION). The rest is fine (but the call-convention/linkage part being dialect specific).

The USING clause needs to be adjusted - only BY REFERENCE (default) or BY VALUE, only identifier (with identifier being a level 01/77 data-item in LINKAGE SECTION). The rest is fine.

Internal Compiler Error on ENTRY statement with invalid USING

As likely kown that is "ice-invalid" (internal compiler error on invalid code). cobc should error when using anything but data-items for the USING clause. Interestingly gcobol has the exact same issue :-) I'll fill a bug report for that as well.

ESQL: double-free in vcache

ESQL: double-free in vcache

ISO/IEC CD 1.1 1989:202x (January 2026, will likely be 2026/2027 standard) The main changes are as follows: The following were general enhancements: Usage BINARY QUAD data items have been added The CONSTANT entry has been changed to allow calculation of length in bytes or characters according to the space allocated to certain specific usages. A derived file feature to allow the contents of one or more files, called contributing files and including derived files, to be concatenated forming the derived...