RE: SQL0243 after V5R4 upgrade?

This is odd:

ASENSITIVE
Specifies that the cursor may behave as SENSITIVE or INSENSITIVE depending
on how the select-statement is optimized. This is the default.

That's from the docs. My cursor is defined as:

DECLARE C1 DYNAMIC SCROLL CURSOR FOR S1

Also from the docs:

Syntax alternatives: The following keywords are synonyms supported for
compatibility to prior releases. These keywords are non-standard and should
not be used:

DYNAMIC SCROLL is a synonym for SENSITIVE DYNAMIC SCROLL

I changed it to:

DECLARE C1 INSENSITIVE SCROLL CURSOR FOR S1

And it's fixed. Wow.. that's weird. Did IBM break something or was it
something I just didn't find that was in the bowels of the docs...lol.

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

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of David Wright
Sent: Monday, October 13, 2008 10:09 AM
To: Midrange Systems Technical Discussion
Subject: Re: SQL0243 after V5R4 upgrade?


On Mon, Oct 13, 2008 at 7:19 AM, Bradley V. Stone
<bvstone@xxxxxxxxxxxx>wrote:

There's no "sensitive" defined in these.. they're average SQL

statements..

They do a union on two files which is about it.

I am guessing your UNION causes the SQL processor to create a temporary
results table, and SQL is throwing an error because the data used
to create
the temporary table could be stale.

Does the code attempt to update/delete records returned by the Cursor?
--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.