RE: Single level store & record blocking on update files (was RE:Where is IBM?)

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

-----Original Message-----
 
--- 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