COBOL code - END-EXEC without dot closing EXEC SQL INCLUDE causes syntax error

[PavelKondratiev]

See self-explaining screenshot below. It does occur for DECLARE.

[FALLAI-Denis]

Hi,

In fact, it depends on whether the use of the COBOL integrated (called) Db2 coprocessor or the standalone Db2 preprocessor.
With the Db2 preprocessor, periods after end-exec are optional and ignored if present (even in procedure division).
However, with the Db2 coprocessor, periods after end-exec are treated as COBOL periods and mark the end of a COBOL sentence.

See Differences in how the Db2 precompiler and coprocessor behave.

The period is mandatory on the end-exec of an sql include:
Using SQL INCLUDE with the Db2 coprocessor

That said, it seems preferable to follow the syntax of the Db2 coprocessor, therefore making the points mandatory after the end-exec of an exec sql include in data division. It is optional in procedure division, (because in this case it is COBOL points which mark the ends of sentences).

See also:
COBOL applications that issue SQL statements

Based on my tests, the dot after end-exec is not mandatory on a exec sql declare cursor , even in Working-Storage Section, probably because it is not an instruction, but a directive (no associated code).

For me, Z Open Editor behaves correctly:

• mandatory dot after end-exec of the exec sql include,
• optional dot after end-exec of the exec sql declare cursor.

Regards.