|
Dan, I did understand your question; I was just trying to answer your question about the iSeries architecture. S/36 used VSAM files. They were located in a contiguous area on the disk. That made blocking much easier there. Been away from coding too may years to comment on record blocking in RPG on the iSeries. I'll let the RPG experts comment on that. Regards, Mike Shaw -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan Sent: Wednesday, April 23, 2003 6:21 PM To: Midrange Systems Technical Discussion Subject: RE: Single level store & record blocking on update files (was RE: Where is IBM?) Mike, Thanks for the reply, but I'm not sure I understand your point. The S/36 allowed record blocking in memory for an update file, and even allowed double buffering in lowly RPG-II. If you blocked 200 records, and you updated those 200 records without accessing any other records in the file, and updated them multiple times, all of that updating took place in memory. The disk didn't see it until either a request for a record outside of the block took place, or the program ended. I benchmarked it and proved it. On the AS/400, there is no record blocking for update files, period. I fail to see why this is, especially in light of the AS/400's single level store. - Dan --- Mike Shaw <mhshaw@xxxxxxxxxxxxxxxx> wrote: > Dan, > > This is because all storage on the iSeries, whether it be main storage > (memory) or auxiliary storage (disk) is addressed as if it were ALL > residing in main storage. This even goes back to the System/38 days. > > Dr. Frank Solits' books "Inside the AS/400" and "Fortress Rochester" > does a great job of explaining this in very simple terms. > > Yup, it's a virtual machine! :-) > > Regards, > > Mike Shaw __________________________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo http://search.yahoo.com _______________________________________________ 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.cgi/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.