|
My perspective on using data areas is that they should be read mostly / update rarely.I don't argue with that. It's mostly what I've used them for also.
This is key to the idea of using them for configuration options that don't get updated often.
In the specific case we were READING journals and keeping track of where we were in the Journal with a *DTAARA! In most cases I would agree with you.if you are updating the *DTAARA with (say) current record position inWouldn't journaling be more appropriate for that kind of functionality anyway?
a massive table (for crash recovery for example) then EVERY record
position gets forced to disk and that slows the job *DRAMTICALLY.
david
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.