Re: power line (AS/400) article in computerworld

["Steve Richter" <stephenrichter@xxxxxxxxx>]

On Fri, Apr 11, 2008 at 11:54 AM, Mark S. Waterbury
<mark.s.waterbury@xxxxxxx> wrote:
> Steve:
>
> You got much of what you have been asking for with the recent new
> hardware announcements and pricing. (POWER = i + p)
>
> But your posts on this list over the past few months indicate a profound
> lack of understanding of just what Single Level Storage and MI
> architecture is all about.
>
> You keep harping on the 16MB segment size as if it is a huge problem. It
> is not. If you truly need to address more than 16MB of contiguous
> storage, you can use teraspace (since V4R4).

read this response to a question of mine from an IBMer

http://groups.google.com/group/comp.sys.ibm.as400.misc/browse_thread/thread/fad53a03aa512d47#

"...Yes pointers are used heavily.  Performance and security main reasons
for spool.  Sadly with rewrite of spool internals in V6R1, some pointer
usage had to be replaced resulting in some performance degradation.
This was due to the implementation needed to improve IPL performance and
concurrent access performance within spool.  Additional checking logic
had to be put in place to prevent spoofing and usage of stale references.

16 meg limited spaces has caused some problems for development, hence
teraspaces and mapped memory objects are used when contiguous storage
beyond 16 meg is required.


I suspect that more problems are now coming up with teraspaces and 4
byte integers.  One can only reference 2 or 4 gig of memory with 4 bytes.  ..."

-------------------------------------------------

what I read from this is the multiple memory models of the system,
teraspace, SLS, mapped memory objects, is weighing the system down in
terms of the incompatibility of system code modules and standards.
And I am not including the reference memory model of the JVM.