|
Mark, check the November issue of AS400 Magazine's Spotlight column when it comes out.... Don in DC On Mon, 18 Sep 2000, Mark Allen wrote: > Since this has come up here and I have been trying to find a "simple" way > (i.e. like journaling, no program changes) to find out who has "read" a file > and since Simon brought it up in his reply, does anyone have an idea of how > to in essence "journal" read op's??? > > Mark Allen > IS Manager > Kelly's Kids > markallen@kellyskids.com > > -----Original Message----- > From: owner-midrange-l@midrange.com > [mailto:owner-midrange-l@midrange.com]On Behalf Of Simon Coulter > Sent: Monday, September 18, 2000 1:05 AM > To: MIDRANGE-L@midrange.com > Subject: Re: Journaling > > > Œ > Hello David, > > You wrote: > >But - Andersen bothered to build in the journaling properly. Part of this > >is to open files for input only where possible. Files opened for update > >will have all their reads journaled. So... MACPAC would often open the > same > >file multiple times - once for read only operations, once for updates. > This > >minimized the impact on the journals. > > While I agree with most of what you wrote, this statement is silly. READs > are never > journalled, what would be the point! I know some sites want to know who > read a record > but journalling isn't the way to accomplish that. Journalling has no effect > on reads. > Even reads though an update ODP. > > Regards, > Simon Coulter. > > «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«» > «» FlyByNight Software AS/400 Technical Specialists «» > «» Eclipse the competition - run your business on an IBM AS/400. «» > «» «» > «» Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 «» > «» Fax: +61 3 9419 0175 mailto: shc@flybynight.com.au «» > «» «» > «» Windoze should not be open at Warp speed. «» > «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«» > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.