Hi,

Dank schneller PMR Hilfe habe ich die Lösung:

Seit V5R3M0 muss man statt dem DYNAMIC Scroll von V5R2
jetzt ASENSITIVE SCROLL definieren.

Zu finden in den Benutzeranmerkungen der Releasedokumentation.


3.44.3 DYNAMIC keyword handled as if SENSITIVE DYNAMIC has been
specified

For V5R3, the sensitivity and scrollability attributes that can be
specified in DECLARE CURSOR and in the ATTRIBUTES clause are being
expanded to more closely match what other DB2 UDB platforms support.
This change exposed an incompatibility between what is done on the
iSeries and what is specified in the SQL standard.

In releases prior to V5R3, the DYNAMIC keyword modified a scrollability
option, and indicated that a scrollable cursor can be used for updates.
In the SQL standard the DYNAMIC keyword modifies a sensitivity option.

For V5R3, the DYNAMIC keyword will be handled as if SENSITIVE DYNAMIC
had been specified. For existing applications that specify DYNAMIC
SCROLL, this will have the desired effect of specifying a scrollable
cursor that can be used for updates.

These changes will cause the following compile-time and runtime
differences in V5R3:

* The syntax INSENSITIVE DYNAMIC SCROLL will not be allowed in V5R3.
The SQL precompiler will signal an error at compile time.
* A cursor declared as DYNAMIC SCROLL in V5R2 is ASENSITIVE. In V5R3,
it will be SENSITIVE. The difference between the two is that an error
is signaled for a SENSITIVE cursor if a sensitive cursor cannot be
implemented. For an ASENSITIVE cursor, an insensitive cursor is
implemented and no error is signaled.
* If a cursor was created in a prior release declared as DYNAMIC SCROLL
and the query implementation would require the creation of a
temporary result table, a runtime error will be signaled. Conditions
that require the creation of a temporary result table are listed in
messages CPI4324 and CPI4325 in message file QCPFMSG.



Wann ist eigentlich endlich Freitag ?

Rince