MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » February 2014

Re: Need To Journal Files & System Impact



fixed

On 21-Feb-2014 13:18 -0800, CRPence wrote:
On 21-Feb-2014 12:27 -0800, Gord Hutchinson wrote:
Is this a recent change? I was always under the impression that
you could only use one journal in a commitment definition.

<<SNIP>>


FWiW: Beyond the doc links offered in the above quoted message [though snipped above, so refer to <http://archive.midrange.com/midrange-l/201402/msg00600.html> for those links], see this additional doc link for a consideration about difference in operation between _same journal_ and otherwise:

IBM i 7.1 Information Center -> Database -> Programming -> Database programming -> Managing database files -> Recovering and restoring your database -> Recovering data in a database file -> Ensuring data integrity with commitment control
_Usage notes: Commitment control_
"...
You can open logical files for output under commitment control when underlying physical files are journaled to different journals. ...

However, the checks for violations are deferred if a record change affects underlying physical files that are journaled to the same journal. If the record change affects underlying physical files that are not journaled to the same journal, and it causes a duplicate key or referential constraint violation, an error will occur during the input/output operation. ...
..."






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact