Re: Log file of file changes -- MIDRANGE-L

Subject: Re: Log file of file changes
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Wed, 30 Oct 2013 13:38:26 -0700
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 10/30/13 12:43 PM, Jeff Crosby wrote:

We had an issue recently about how a couple of prices got changed.
<<SNIP>> suggested a log file of changes. <<SNIP>>

The file is currently journaled, but that's not really what
journaling is for, IMO.

FWiW: The origin of the name for the object type *JRN, and the *JRNRCV into which /journaled changes/ are deposited, were conspicuously chosen for the definition of the term; i.e. indeed, that is a primary purpose of the journal feature, and this capability to journal changes is a pre-requisite for commitment control [aka isolation]:

http://dictionary.reference.com/browse/journal
" _journal_
...
noun
1. a daily record, as of occurrences, experiences, or observations: ..."

FWiW, see Compare Journal Images (CMPJRNIMG) command for a limited-feature reporting interface.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.