Re: Copying code into SQL statements

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

I believe I understand what you are asking.  I just cannot see where I'd
ever use that technique.  And I think any "Idea" request would get shot
down.
I think the alternative might be an external data structure based off of an
appropriate view.


On Fri, Mar 21, 2025 at 4:09 PM x y <xy6581@xxxxxxxxx> wrote:

> 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!
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.