|
Why do you believe journaling in most iSeries shops is a rare practice?--
Our
shop journals all important files (or tables as I'm trying to start
calling them!).
I was also under the impression, which might be incorrect, that High
Availability software requires journaling on.
Larry
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
Sent: Thursday, August 20, 2009 11:33 AM
To: Midrange Systems Technical Discussion
Subject: Re: Modernizing applications (was: Explaining single level
store to non ipeople)
I would think jounalling in most iSeries shops is a rare practice.
On Thu, Aug 20, 2009 at 11:16 AM, Mike Cunningham
<mike.cunningham@xxxxxxx>wrote:
When you talk journaling here are you talking about databaseas
journaling
in STRJRNPF? Since the first day we had our first S/38 we haveotherwise.
journaled every file except some temporary work files. Isn't that a
fairly common practice? And isn't the default for any table created
via DB2 SQL to have journaling on?
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Thursday, August 20, 2009 10:37 AM
To: Midrange Systems Technical Discussion
Subject: Re: Modernizing applications (was: Explaining single level
store to non ipeople)
Lucas,
After some off-line discussion with another list member and some
research of my own, and also because of your reply, I'm convinced
that SAP does do some form of journaling, and would now be very
surprised to learn
And that would partly explain the higher throughput I'm getting.Users
I'm not journaling. I'm not using commitment control - in this case.
On the other hand, as I explained earlier, my order entry
application creates an order, then creates one or more line items, individually.
press enter, a line item is created, the item is added to a table onchange,
the screen.
After users exit "add" mode, they may select multiple line items to
and enter a cycle where each line item is pulled up individually onmultiple
the screen, and changed individually.
I understand that other developers may use a different model where
records are entered or changed as a batch, then eventually posted as-
a batch, but I don't use that model, and wouldn't recommend it either.
However, I'm planning on using commitment control on my next
application
GL Journal Entry, to ensure that debits & credits balance (meet ACIDEach
requirements).
HTH,
Nathan.
----- Original Message ----
From: Lukas Beeler <lukas.beeler@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, August 19, 2009 11:19:10 PM
Subject: Re: Modernizing applications (was: Explaining single level
store to non ipeople)
On Wed, Aug 19, 2009 at 23:22, Nathan Andelin<nandelin@xxxxxxxxx> wrote:
use full commitment control and journalling for everything
It would really surprise me if SAP's benchmarks included journaling.
They do. tlogs aren't optional in other RDBMS. Except in MySQL with
MyISAM tables, which is a special case.
But my order entry applications follow a traditional header-linewhere the order is entered, then a series of line items are entered.
model,
entry adds or changes a record on the server, immediately.But
And there is never ever any need in your application to change more
than one row at a time?
Under my header-line model, there's no need for commitment control.
RPG-based commitment control doesn't add much overhead, if or whenneeded.
to
Well, i don't see ACID in a business critical application as "optional".
Well, I subscribe to the old adage - make everything as simple aspossible. In this case, the IBM i HTTP server forwards browser
requests
an RPG-based server which natively interfaces with the database,list
then returns an HTML/JavaScript response.
Yep, but "Notepad is faster than Word" is hardly news. Even if the
machine running notepad is slower.
--
Read my blog at http://projectdream.org
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,list
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
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,list
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
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.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
