|
I've stared at this simple select statement until I've gotten a
headache. It must be something simple that I've missed. This is the
syntax:
WITH
temp (balance,cus#) AS
(SELECT field1+field2+field3 AS balance,cus#
FROM lib.file)
SELECT *
FROM temp
WHERE balance>0
The processor doesn't like the '>' but I believe it's actually
pointing to a problem with my mapped field - balance. I've
substituted = for>; it still throws the same error (SQL0104).
However, if I run the script eliminating the WHERE clause in the
full-select, it runs nicely returning both columns as I think they
should look.
I hate arguing with script processors. BTW, I'm doing this using
System i Navigator.
As an Amazon Associate we earn from qualifying purchases.
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.