Re: 7.1 gets stricter on SQL -- MIDRANGE-L

Subject: Re: 7.1 gets stricter on SQL
From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Date: Mon, 31 Jan 2011 14:01:57 -0600
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 1/31/2011 1:53 PM, Joe Pluta wrote:

That may well be what I need, Luis. Thanks for that. However, I've been VERY unsuccessful setting QAQQINI options. In fact, the last time I did it my queries stopped working at all.

I tried this:

update qusrsys/qaqqini set qqparm = '*YES' where
qqparm = 'COLLATE_ERRORS'

and I got a trigger error CPF433B, code 3, with text "Parameter *YES was not valid".

Not enough hours available today to chase that one down.

Joe

Ah pfui. That was dumb. Should have been set QQVAL = '*YES', not QQPARM. Duh. Anyway, I did that and it didn't fix the problem. Not sure why or why not, and as I said, I don't have enough hours today to chase it down.

Joe

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.