Non-Logged Operations on DB2/400 -- MIDRANGE-L

Subject: Non-Logged Operations on DB2/400
From: "Ryan Hunt" <ryan.hunt@xxxxxxxxxxxxx>
Date: Mon, 19 Sep 2011 11:11:09 -0400
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>

I am writing some external integration code that will be runing outside of
the AS400. It will be doing lots of data modification via native SQL
interface (over ODBC) - would prefer to avoid the QSYS.QCMDEXC interface if
possible.

I will be doing lots of data mods overnight - that do not need to be
logged - on tables that are currently journaled. I have tried the ALTER
TABLE statement with the INITIALLY NOT LOGGED option but it doesn't seem to
make a difference.

I'm looking for suggestions on how to either temporarily turn off journaling
(via SQL) on journaled tables, or perform non-logged operations (again, VIA
SQL).

I don't mind resorting to QCMDEXC if I really need to.

Thanks!

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

AW: Non-Logged Operations on DB2/400 , Birgitta Hauser
Re: Non-Logged Operations on DB2/400 , rob

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.