RE: Paging file

Well, to put same thing in slightly different way:

The single-level store was one of the THE most advanced concepts that was
DESIGNED and built into the S/38 architecture.

Especially since it was back in the days when mainframes were KING, and
files were located by disk volumes, cylinders, and tracks...  Recall
"extents" being an issue, back when I learned.  Don't know about *nix then,
(nor not enough about it now).


S/38 CPF (aka OS/400) objects were and are located by name and object type.
That's all You need.

The key is that "other than for performance issues", Your entire disk is
considered one HEEEEEEEEEOOOGE block of memory accessible at any time,
"automagically".  DOES NOT MATTER where something is...  Memory, cache,
registers, or disk...  And the OS and compiler developers SURE **sweat these
kinds-a details for us**, and that's one LUCKY thing for sure...!

That's also why You don't generally need a bunch of complicated memory
allocation and garbage collection routines involved in application
programming on an iSeries.  (Although they are available, for example if You
need them for porting systems...;-)  I haven't kept up on the technology ALL
that much, so don't know exactly how much of this stuff is going on at the
hardware level.  I gather a LOT is, because the iSeries SURE excels at Java
and some of those benchmarks.

And btw, my understanding is that this is one-a the PRACTICAL advantages of
the CPF/OS/400 "object-based architecture" (as opposed to OO design or
programming, which is different).  IOW, having a uniform method of accessing
all objects.


>From what I know, the mainframes have advanced a fair bit.  But OS/400 still
leads ALL the rest by far in this regard, still...


| -----Original Message-----
| [mailto:midrange-l-admin@midrange.com]On Behalf Of Booth Martin
|
| please...  more discussion on this, more explanation.
|
| Love the concept, love the results, haven't figured it out though.
|