No Subject

[bmorris@xxxxxxxxxx]

Rolf Mittag wrote:

>Just a warning added :
>don't try it with embedded Sql. The Sql precompiler ignores
>conditional compile options at least everytime I tried it. Since
>it is strongly recommended to use Sql for DB access the whole
>conditional compile stuff is almost wothless.

Rolf, if you're having a problem with SQL and copy files
containing conditional compilation directives, the RPG compiler
has PTFs for V4R2 and V4R4 that allow you to use /INCLUDE instead
of /COPY.  The SQL pre-processor will ignore /INCLUDE so it won't
try to look inside the copy file, but the RPG compiler will see it
when it compiles the generated RPGLE source.

In RPGLE source, it doesn't matter which one you use, /COPY or
/INCLUDE - they both mean the same thing; in SQLRPGLE source,
you would use /COPY if SQL needed to see inside the copy file,
and you would use /INCLUDE if SQL got upset by what was inside
the copy file.  Otherwise, use whatever you want.

Release       |     PTF
--------------+-------------------------------
V4R2, V4R3    |     SF62167
V4R4          |     SF61918 for TGTRLS(*CURRENT)
V4R4          |     SF63132 for TGTRLS(*PRV)

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
+---