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



Nevermind. Figured it out myself.

It was the SQL Rules option, I changed from *STD to *DB2 since the last time
I ran this SQL, when I changed it back to *DB2 it worked.

But, it makes me wonder how it would work using *STD rules.



On 4/4/07, Ron Adams <rondadams@xxxxxxxxx> wrote:

I have a field that is randomly being populated with "+" (plus sign) near
the end of the field.

I previously asked how to find the errant rows using SQL and the response
was given:
use LIKE X'6C4E6C' which worked fine at V5R3, but since we've switched
to V5R4 it doesn't seem to work.
The error message I get from SQL is "Operands of LIKE not compatible or
not valid."

Any thoughts?
Here's my (previously working) SQL:
SELECT PLT, ITMID, MAJLOC, MINLOC FROM abcdta.dcsilm WHERE MINLOC
LIKE X'6C4E6C'

--
Ron Adams





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.