Hi Pete

It might help to put a monitor on it - you can filter it down to job names, QZDASOINIT, maybe here.

Maybe the error will appear in order with the statement that generated it - worth a shot, eh?


On 10/1/2012 10:40 PM, Pete Helgren wrote:
I have a customer with an app that connects to the i with ODBC. It is
an ancient application running on Windows NT but has worked flawlessly
for a decade. They upgraded to V7R1 from V6R1 and now they get the
following on any SQL invoked by the ODBC connection:

Message ID . . . . . . : SQL0084 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 10/01/12 Time sent . . . . . . :

Message . . . . : SQL statement not allowed.
Cause . . . . . : The SQL statement is not allowed for one of the
reasons: <Lists a bunch of reasons here>

Of course, stating what the offending statement IS apparently isn't part
of the error reporting so I don't know which of a few hundred SQL
statements it is complaining about. I am assuming it is the initial
CONNECT but I can't be sure.

Anyone run into this? I can find much in the Memo to Users that refers
to ODBC or SQL0084


Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2015 by MIDRANGE dot 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 here. If you have questions about this, please contact