Re: AW: Strange SQL error

Hi,

According to the SQL reference 6.1. CLIENT became a restricted word in
Release 6.1. (Appendix I)
The double quotes around the column name in your files and views get
automatically set by the system.
But your embedded SQL source code is not changed automatically. That's why your statement failed.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Pete Helgren
Gesendet: Monday, 12. January 2009 18:25
An: Midrange Systems Technical Discussion
Betreff: Strange SQL error

I have some SQL code that has been running for ages that suddenly stopped working. It is very curious.

The statement is:

select LISTID FROM AARRLISTH WHERE USERID = 'PETE' AND DOCTYPE = 'AFREQ' AND CLIENT = 'HKSD'

The error is:
Token = was not valid. Valid tokens: <IDENTIFIER>.

I ran the statement using interactive SQL and the cursor was positioned at the equal sign just after the column name CLIENT. When I prompt, I see the column CLIENT listed as "CLIENT". It has quotes around it.

The curious thing is that this code hasn't been changed for a couple of years and I never got this error.

So my assumption is:

1. Dumb luck. This never should have worked.
2. CLIENT is now a restricted keyword and it wasn't before (this first failed on my customers' V5R4M0 box which is WAY behind on PTF's. It also fails on my V6R1M0 box which is absolutely current.)
3. Someone changed the column name from CLIENT to "CLIENT" (how it occurred on two different boxes would be a mystery though).

Ideas? Why would this suddenly fail ?

Pete