|
<<SNIP>>
The use of separate host variables is fine, so long as you always
have the same number of values to check. Or if you have enough host
variables to handle the maximum number of such values. I think it'd
work to have values that are all blanks when you are testing only 2
but could have up to 5, say. The test would still succeed, because
you'd match one of the items - IN is effectively a set of OR
operators.
The alternative of dynamic SQL allows for any number of values, of
course.
On 2/12/2013 1:32 PM, CRPence wrote:
On 12 Feb 2013 10:50, Rettig, Roger wrote:
I have a SQL clause embedded in a RPG program. The statement<<SNIP>>
inserts records directly into a file. In the where clause, I have
an 'in' statement <ed: IN PREDICATE> using a variable:
WHERE pypmtt in :CheckType
<<SNIP>>
Basically what is required instead, is to code the following,
where the CkTyp## variables are compatible with the column pypmtt:
WHERE pypmtt IN (:CkTyp01, :CkTyp02)
What is returned from the following input used for a Google web
search will likely prove helpful:
"in predicate" "host variables" site:archive.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.