Re: SQL0084 after upgrade to V7R1 on ODBC connection

[Pete Helgren <pete@xxxxxxxxxx>]

I finally resolved this and it WAS an issue with the *SQLPKG .  I 
thought I had deleted the old packages after the upgrade but it turns 
out they have a few ODBC connections and the packages I deleted weren't 
the ones for my application.  I found the packages in my RPG object 
library, right where I told the ODBC driver to put them :-|

The DBMON stuff that was suggested was excellent BTW and the query that 
Vern posted produced some great information on the db queries running on 
the connection so it was a worthwhile endeavor from a learning perspective.

Posting now that IBM confirmed the issue and it has been solved (months 
later). FYI.

Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java

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  . . . . . . :
> 16:31:12
>
>    Message . . . . :   SQL statement not allowed.
>    Cause . . . . . :   The SQL statement is not allowed for one of the
> following
>      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
>
> Thanks,