Re: SQL error -- MIDRANGE-L

Subject: Re: SQL error
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Fri, 07 Dec 2012 08:36:53 -0600
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 06 Dec 2012 23:25, Birgitta Hauser wrote:

Tables in QTEMP are never journaled and you are running the statement
in an environment where commitment control is started and used.
To avoid this error messages you may add WITH NC (= With No Commit)
to the end of the statement.

I often will journal a TABLE in QTEMP, so assuredly the claim "never" is false, given that counter example. I do not recall, but I believe the QDFTJRN could also be used for implicit journaling for the QTEMP library; when I journal, I typically use QCMDEXC to STRJRNPF. Additionally, if the TABLE was created as a GLOBAL TEMPORARY TABLE, using the appropriate syntax, even that would have the TABLE implicitly journaled; GTTs are created in [IIRC] the SCHEMA named SESSION which is just a synonym for QTEMP.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: SQL error , Stone, Joel

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.