What are they using for an ODBC driver?
I haven't encountered this issue, but my first impulse would be to install the ODBC driver from Navigator for 7.1 and configure the application to use that driver. Is NT supported by that driver? I don't know.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Monday, October 01, 2012 10:41 PM
To: Midrange Systems Technical Discussion
Subject: SQL0084 after upgrade to V7R1 on ODBC connection
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
Value Added Software, Inc
GIAC Secure Software Programmer-Java
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l