Re: Non-Logged Operations on DB2/400

No replication. No need to roll anything back. We are pushing massive
amounts of data into an isolated ledger type (part of the composite key)
within an ERP table. If there is an issue with the data it is always a
delete and insert, no update. The table (and others) are journaled because
there are other ledgers managed by the ERP that absolutely need journaling.

These ERP tables have a primary key but no foreign keys or check
constraints. All integrity (other than PK) is maintained at the application
level (much to my chagrin).

Anyway, I am safe to do what I am trying to accomplish.


<rob@xxxxxxxxx> wrote in message
news:OF37AB814D.1317912B-ON85257910.00542312-85257910.0056CE6F@xxxxxxxxx...

If you're logging for data replication (like Mimix) you'll have to resync
the databases if you do this.

If you manage to turn off logging and you really screw this up you will
not be able to do either a ROLLBACK or RMVJRNCHG to fix it.

You'll have to handle the lock of the file during this. For example if
you prompt ENDJRNPF and see that CPF7031 is one message that can be
monitored.

Does the table have any constraints or referential integrity which forbid
this?

But I think you'll be limited to QCMDEXC and ENDJRNPF and STRJRNPF.

Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Ryan Hunt" <ryan.hunt@xxxxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 09/19/2011 11:16 AM
Subject: Non-Logged Operations on DB2/400
Sent by: midrange-l-bounces@xxxxxxxxxxxx



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!



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email:

MIDRANGE-L@xxxxxxxxxxxx

To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email:

MIDRANGE-L@xxxxxxxxxxxx

To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.