MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » February 2014

Re: Need To Journal Files & System Impact



fixed

Yes, Thanks Chuck.

We've never needed to have files journaled to multiple journals used in the
same commit cycle. This is going to be changing soon so this is very
timely information.


Gord




On Fri, Feb 21, 2014 at 4:27 PM, <rob@xxxxxxxxx> wrote:

Appreciate that Chuck. It's nice to know we weren't totally off our nut -
even though darn few of us probably ran commitment control under V2R3. I
can see the flip side that it's sad it's taken us so long to learn that -
like the coworker (now retired) who didn't know you could run CHGPF, with
DDS, instead of having to do all the CPYF crap and whatnot manually.
Probably because there's still few of us using commitment control in their
daily applications. Oh well, we can always blame it on the vendors...


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
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: CRPence <CRPbottle@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Date: 02/21/2014 04:18 PM
Subject: Re: Need To Journal Files & System Impact
Sent by: midrange-l-bounces@xxxxxxxxxxxx



A restriction removed so long ago, I can not recall when. But...

Being persistent, I found the below quoted snippet of text in the
v5r1 Backup and Recovery Guide (B&R Gd) which suggests the answer is
since v3r1, and that quoted text follows the link to that document
included immediately below:
<http://publib.boulder.ibm.com/iseries/v5r1/ic2924/books/c4153045.pdf>
"...
_How Should Objects Be Assigned to Journals_?
You can use one journal to manage all the objects you are journaling.
Or, you can set up several journals if groups of objects have different
backup and recovery
;;; Chapter 19. Planning and Setting Up Journaling Page: 391
requirements. Every journal has a single attached receiver. All journal
entries for all objects being managed by the journal are written to the
same journal receiver.

When deciding how many journals you should use and how to assign objects
to journals, consider the following:
...
* If you have Version 2 Release 3 Modification 0 or earlier of the
OS/400 licensed program, all files opened under the same commitment
definition within a job must be journaled to the same journal. If you
have Version 3 Release 1 or later, this restriction no longer applies in
most situations. In commitment control, each journal is considered a
local location. Table 75 on page 544 describes what conditions are
required for more than one local location (journal) to be allowed.
..."

The above correlates with the InfoCenter doc link provided earlier by
Charles [reinserted here with the drill-down path included]:
IBM i 7.1 Information Center -> Systems management -> Journal management
-> Local journal management -> Planning for journal management ->
Planning setup for journals
<

http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzaki/rzakiobjassnjrn.htm

_Object assignment to journals_

Regards, Chuck

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.

On Thu, Feb 20, 2014 at 3:58 PM, Charles Wilt wrote:


I must admit, I also thought there was an issue with using
multiple journals in the same transaction...

But I see only a recommendation:

- To simplify recovery, assign objects that are used together
in the same application to the same journal.

Along with a confirmation of what you indicated

- Files opened under the same commitment definition within a
job can be journaled to different journals. In commitment
control, each journal is considered a local location.

<

http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzaki/rzakiobjassnjrn.htm



--
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.









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