SQL0243 after V5R4 upgrade? -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Getting this error on a customer's machine running some dynamic SQL
statements after upgrading to V5R4 this weekend.

There's no "sensitive" defined in these.. they're average SQL statements..
They do a union on two files which is about it.

I'm guessing they didn't apply the latest CUM, but waiting to hear.
Amazingly, nothing in the archives about this so I'm just throwing it out
there to see what others may know.

Message ID . . . . . . : SQL0243 Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 10/13/08 Time sent . . . . . . : 09:03:17

Message . . . . : SENSITIVE cursor C1 cannot be defined for the specified
SELECT statement.
Cause . . . . . : The cursor C1 is defined as SENSITIVE but the query
requires the creation of a temporary result table. A SENSITIVE cursor
cannot be implemented.
Recovery . . . : Redefine the cursor as ASENSITIVE or INSENSITIVE or
change
the query so that it no longer requires the creation of a temporary result
table.

Bradley V. Stone
BVSTools - www.bvstools.com
eRPG SDK - www.erpgsdk.com

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.