Re: Conditional Compiler Directives and CRTSQLRPGI

>Date: Mon, 24 Apr 2000 14:46:22 -0500
>From: bellis@ORIENTAL.COM
>
>We are using Conditional Compiler Directives extensively in our RGPLE
source
>member to define procedure parameter, prototype and interfaces before
including
>copy book source.
>
>
>These work wonderfully with straight RPGLE modules and programs.
>However, when we try to use embedded SQL, the SQL precompile fails.
>The error we get is:
>SQL1106  30     129  RPG specification out of order.
>
>What appears to be happening is that the SQL precompiler is ignoring the
>Conditional Directives and including all of the source in the copy book.
>
>Is there a compile option we are missing on the CRTSQLRPGI command?
>If not, Is there a PTF out there to fix it or some other work around?

Brian, there IS a PTF that alleviates this problem.  The PTF allows you
to use /INCLUDE instead of /COPY.  When SQL sees the /INCLUDE, it doesn't
open up the copy file.

You can use /INCLUDE in both RPG and SQLRPGLE code.  In SQLRPGLE code, you
would only use /COPY when you wanted SQL to see the code.

The PTFs are:
VRM420  SF62167 - available
VRM440  SF61918 - available within the next few days, I hope

The TGTRLS(*PRV) PTFs are not available yet.  SEU and CODE/400 will not
recognize /INCLUDE until
a future non-PTF release.

Barbara Morris


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---