× 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.



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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.