RE: SQL0601 issued when WITH REPLACE was specified ?

Chuck:
I don't know the answer on updates but I'm taking your information to our operations manager.
I believe our production lpar is some 12 months behind.

Thank you for the APAR\PTF lead !

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Friday, June 19, 2015 2:01 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: SQL0601 issued when WITH REPLACE was specified ?

On 18-Jun-2015 12:14 -0600, Gary Thompson wrote:

V7R1M0

And TR, cumulative, group levels? A rather old APAR\PTF with the symptom msgSQL0601 F/QSQCRTI for a GTT: SE53979 \ SI48641 [http://www.ibm.com/support/docview.wss?uid=nas2eebf90faae4964ed86257ab70041f561]
[http://www.ibm.com/support/docview.wss?uid=nas3dedc4f433ae7319286257ac70000b8a3]

I'm testing a change to an SQLRPGLE which has been in use for some
years.

The program object was created using PDM work with Objects to copy the
program from a production lib into a special test lib I'm using just
for this test.

I'm wondering why I received SQL0601 on the following embedded SQL:

DECLARE GLOBAL TEMPORARY TABLE lcp980wk1
( delloc CHAR(4) NOT NULL,
<<SNIPped>>
)
WITH REPLACE NOT LOGGED

My assumption was "WITH REPLACE" would allow the table to be replace
in the event it exists ?

That is the purpose of the clause.

Would it be better practice to start with a DROP command ?

Precede the DECLARE with a DROP statement, probably only in supposing there is a defect to overcome; i.e. as a circumvention. FWiW, if the attempt to DROP TABLE QTEMP/lcp980wk1 RESTRICT [after the -601 error] fails due to restrictions, then that gives support for the APAR\PTF noted; i.e. the default of CASCADE for DROP ignores the /restriction/.

p.s. the topic seems purely SQL; unlikely to be specific to RPG

--
Regards, Chuck

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.