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

Subject: Re: Non-Logged Operations on DB2/400
From: rob@xxxxxxxxx
Date: Mon, 19 Sep 2011 11:48: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>

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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Non-Logged Operations on DB2/400 , Ryan Hunt

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.