🚀 go-pugleaf

In article <1026@maxim.erbe.se> prc@erbe.se (Robert Claeson) writes:
>In article <461@tron.UUCP>, vsg@tron.UUCP (Vax Support Group) writes:
>
>...
>> I have been searching for hardware architecture information on IBM's AS/400
>> system.  Specifically I would like to detailed box diagram showing the main
>> components of the system and the interconnections.  I would also like details
>> about each box and the interconnection.  I have been through 4 IBM sales reps
>> and one technical specialist.  I can't seem to get past the marketing glossies. 
>> I'm beginning to think that this information does not exist.
>...
>
>Well, I've had severe problems just getting MIPS number, benchmark results
>and any performance data from IBM on the AS/400. Seems like they're not
>overly proud of that information...
>
>-- 
>          Robert Claeson      E-mail: rclaeson@erbe.se
>	  ERBE DATA AB

IBM has taken the position that the internal architecture of the AS/400 is
proprietary. There is performance information in the form of benchmark results
(RAMP/C and others), but just about nothing else. If your rep can't find
these benchmark numbers, refer him to the original announcement presentation
they were in it). IBM has published comparative benchmark results for the 9370
versus several other comparable processors (some VAXen and HP 3000's). I believe
they did the same for the AS/400, but I'm not sure. At any rate, since they
used the same benchmark suite and assuming that you can get the AS/400 numbers,
you can use they published 9370 results (IBM Pub. gg22-9423).

As to why they consider the architecture proprietary, who knows? They are
consistant, however as the AS/400 is the followon/replacement for the system/38
and system/36 which had similar restrictions on information. The rumor mill has
it that the AS/400 and the 9370 are in fact the same processor, but who knows?

Disclaimer: All of this was gleaned in my previous job. As far as I know,
Amdahl has no interest in AS/400's and I have no current source of information.

Terry

Disclaimer: all of this was gleaned in my previous jobs. My cuerrent