MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » February 2014

Re: Need To Journal Files & System Impact



fixed

This approach is fine so long as you stick to it, but you could end up with
an awful lot of individual journals. There might be some complications
around CRTDUPOBJ and save/restore between libraries (if you do that) that
might also complicate what journal things end up going to - I have not
thought this through yet.

If you are using the journals for a HA product this becomes terribly
difficult to manage as ideally you want to group common libraries/resources
together in the same journal (at least in my experience).



On Fri, Feb 21, 2014 at 8:41 AM, <rob@xxxxxxxxx> wrote:

There are those who will argue that putting the journals and receivers
into the same library as their data also ensures this. That's all well
and good until you start getting cross library transactions you want to
use commitment control on.
I make a sale. I want it to update customer data in ARLIB. I also want
it to update salesperson data in CRMLIB. And I want to use commitment
control. If the operation fails it should roll back the previously
written data. Hard to do when your data resides in two different journals
and journal receivers.


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: Evan Harris <auctionitis@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 02/20/2014 01:46 PM
Subject: Re: Need To Journal Files & System Impact
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Hi

Like Rob I don;t usually worry about setting up an additional ASP for
journalling, but I do try very hard to get the journals and receivers put
into separate distinct libraries, not just dumped into the application
library.

If ar all possible create a library called something like @@JRN to hold
the
journals and @@JRCV to hold the receivers.

The reason for this is to ensure that the receivers and journals are
restored before the supported objects when you are doing a recovery and
journalling is automatically resumed on all object being restored.



On Fri, Feb 21, 2014 at 4:11 AM, <rob@xxxxxxxxx> wrote:

Nice catch.


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: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 02/20/2014 09:49 AM
Subject: Re: Need To Journal Files & System Impact
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Take a look at here



http://www-03.ibm.com/systems/power/software/i/db2/support/code/journal-utilities.html



Journal Sizing and Planning Tool (Pseudo Journal)

Charles


On Thu, Feb 20, 2014 at 6:23 AM, Jack Kingsley
<iseriesflorida@xxxxxxxxx>wrote:

I have a small group of files that I need to start to journal. Is
there
a
way to determine how journaling of these files would impact a system.
Example: How big the journal receiver will get, how many entries, CPU
overhead, should the objects be in the same library, etc. Was not
sure
if
there is a way to determine this or not.
--
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.


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




--

Regards
Evan Harris
--
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