Re: Statically binding multiple MAIN modules with display files

Joe Pluta wrote:
> ...
> The RPG compiler understands the concept of nested source, so when it
> encounters /EOF, it simply stops processing the /COPY member and goes on
> with the rest of the code.  The catch is that the SQL preprocessor does
> NOT understand nesting.  Thus, the first time it hits an /EOF statement,
> it thinks that's the end of the source, and you're done.  Thus, if I
> include anything, the source won't compile.
> ...

Joe, if SQL doesn't need to see inside the /copy file, use /include
instead of /copy.  (The only reason SQL would need to see inside is if
the copy file has embedded sql or definitions of host variables.)