|
--- someone wrote: > What OS/400 adds to that is the concept of single level store, in > which the persistent store (hard disks) is basically considered one > big swap file. Any address in any process can refer to any piece of > memory anywhere within the (necessarily) large address space. Sorry I'm late to this party, this may be a *little* OT, but it's been a niggler for me ever since I abandoned the S/36 decades ago <g>. Given the above statement that I believe was made by Hans (and how convenient that is, since this relates to RPG programs!), I have never been able to understand why the AS/400 does not allow record blocking for update files like the S/36 did. Since the AS/400 looks at the contents in memory and on disk without regard to its actual location, why is this? - Dan __________________________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo http://search.yahoo.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.