× 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 Chuck

I like this a lot - I was thinking of the issue that a blank might be a valid value but did not go that far, since I didn't have another idea - NULL does it nicely.

Vern

On 2/12/2013 3:30 PM, CRPence wrote:
On 12 Feb 2013 11:41, Vernon Hamberg wrote:
<<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.
May be better to use the NULL value versus blanks for the /untested/
values, using embedded SQL for more Host Variables in the IN predicate
than there are actual values specified, if a blank-value is a valid
stored value [and thus could be selected]; similarly for zero-value.
See an example of using NULLIF to request to test against the NULL value
instead of blanks:

# Subject: Re: Using host variables in SQLRPGLE doesn't seem to be
working.... IN clause
# From: CRPence
# Date: Mon, 10 Jan 2011 13:33:38 -0800
http://archive.midrange.com/rpg400-l/201101/msg00145.html

The alternative of dynamic SQL allows for any number of values, of
course.
Agreed. The OP was coding embedded SQL, so I responded with a way to
correctly code [for exactly] what was given, using embedded SQL :-)

FWiW another web search that might also provide some worthwhile links:
http://www.google.com/search?q="in+predicate"+"host+variables"+"embedded";

Among the links returned is the following article which discusses
what Vern addresses above. However I /hate/ the suggestion given, of
using /garbage/ in the extra host variables [just as I noted above for
using blanks] with the intent to avoid selection; Yuck! Just use the
NULL value. I did not even briefly scan the article beyond that.
Volume 5, Number 36 -- September 28, 2005
SQL Record Selection with Dynamic Lists
Author: Ted Holt
http://www.itjungle.com/fhg/fhg092805-story02.html

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
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>>
<<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 thread ...

Replies:

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.