|
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Friday, October 05, 2007 11:54 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: SQL update vs RPG/DDS update
From: Wilt, Charlessuch thing
I'm not sure what your problem is, Gene, but it is not that dirty
records are being hidden from users due to caching.
The beauty of the single level store is that there is no
which case,as a dirty record. When you access a record, you are accessing
address of the virtual memory location where it resides and that
memory is the same for all users.
Not quite true Joe.
Sounds like RPG may be blocking the i/o of the file. In
while the program has done the WRITE, the data is still inthe program
buffers and has not yet been passed to the DB.
I though I was pretty clear about updates vs. writes,
Charles. While writes may be blocked, the random nature of
the CHAIN/UPDATE pretty much precludes any blocking. I
suppose you MIGHT see blocking on an update primary file, but
I haven't tried that in a long time, and anyway that's not
how I read the original post. Gene specifically used the
word "update" which I took to mean updating a record, which
in turn means CHAIN/UPDATE.
On the other hand I suppose it's possible that he was talking
about locking the file and doing a bunch of writes. In that
case, you're absolutely correct that the writes could be
blocked (which I also said), and I would definitely go with
the FEOD strategy; that's what I use as opposed to the FRCRATIO.
Joe
--
This is the RPG programming on the AS400 / iSeries (RPG400-L)
mailing list To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-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.