× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Jay,

try to use the SYSTOOLS.SPLITT table function - I think the syntax is:

where objname in (select element
from table(splitt(:l_objects, ‘,‘)))

but I’m not 100% sure - because I’m out of the office right now.

I used it several times in an application where I needed a „dynamic parameter list“ - works AFAIK on 7.3 and later.

HTH
Daniel




Von meinem iPhone gesendet
Am 18.04.2023 um 18:34 schrieb Jay Vaughn <jeffersonvaughn@xxxxxxxxx>:

I'm doing an embedded rpgle sql select on qsys2.object_statistics, and my
where clause contains...
where objname in (:l_objects)

l_objects = char(2048) and will contain a comma delimited string of
objects, just as sql "IN" would want to see... ie. 'OBJECT1', 'OBJECT2'

in debug it looks fine... I even tried (trim(:l_objects))

However when I run it, I get sqlcode 100.

But if I convert the thing to dynamic sql, i can get it to work. (but I
really don't want to have to do that)...

any suggestions to make it work without dynamic?

tia
Jay
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.