MVSFORUMS.com

[chuck]

Hi
We have a number of programs that are in production where we have this construct in W-S
EXEC SQL
INCLUDE blah
END-EXEC
EXEC SQL
INCLUDE blah
END-EXEC

Note that there is no period after the END-EXEC
These programs, as I said, were successfully compiled, linked and bound and are running in prod.

Recently I had reason to recompile one of these programs in dev and I started getting compiler errors which disappeared once I added the period after the END-EXEC

I was curious if anyone knew of a change in the way the cobol compiler works that would cause this behaviour to change? Did IBM, like, "tighten up" the compiler?

I know that periods are not needed in the Procedure Division

Thanks

[kolusu]

chuck,

Is it the Precompiler that issued the error message when the period is missing or is it the COBOL compiler that issued the message?

According Db2 12 , Period is OPTIONAL if it is in between COBOL statements.

[chuck]

Sorry, should have responded to this. We did discover that stand alone precompiler (DSNHPC?) will ignore the fact that period is missing but if we used integrated precompiler of IGYCRCTL then it will flag it.
So confirms your assumption Kolusu
Thanks