RE: Statically binding multiple MAIN modules with display files

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Barbara Morris
> 
> 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.)

This works great, Barbara.  But, being as I am often a little slow, let
me make sure I understand the limitation: if the included source
contains host variables (that is, variables I use in SQL statements,
like SELECT FIELD INTO :HOSTVAR), then I cannot use /INCLUDE.

For my little brain, this means that /INCLUDE is not expanded by the SQL
preprocessor at all, and just passed straight through to the RPG
compiler.  Because of this, any source inside of /INCLUDE members is
ignored by the SQL preprocessor.

Do I get a gold star?

Joe