Re: Copying code into SQL statements

[Daniel Gross <daniel@xxxxxxxx>]

Hi x,

I cannot see the real advantage of using machine generated include files.

If you simply use an externally described data structure, the RPG compiler automatically generates the fields for you.

Why generate extra include files?

Regards,
Daniel


> Am 21.03.2025 um 21:09 schrieb x y <xy6581@xxxxxxxxx>:
>
> Instead of SELECT * or listing every column name, I'd like to put the
> column names in a source member and "include" it in the main SQLRPGLE
> compile.  The source members are machine-generated; I'm doing this to
> reduce the maintenance workload.
>
> "from_src" is "a,b,c".  "into_src" is ":a,:b,:c".
>
> INCLUDE works with SELECT:
> SELECT
> INCLUDE from_src
> INTO...
>
> but the preprocessor won't accept
> INTO
> INCLUDE into_src
> WHERE...
>
> The error is SQL0104 and the preprocessor is looking for a comma or an
> INTO.  I have my INCFILE set correctly.
>
> Using
> FETCH NEXT FROM THIS_CURSOR INTO
> into_src...
>
> INCLUDE is tagged as a variable not found.
>
> Am I missing something other than using dynamic SQL?  It's just a reminder
> of how incredibly productive DDS is!