• Subject: Re: Proportion of programming languages on AS400
  • From: email@xxxxxxxxxxxxxxxxxxx (James W Kilgore)
  • Date: Mon, 22 Nov 1999 01:16:40 -0800
  • Organization: Progressive Data Systems, Inc.


Geez, you triggered some brain cell that recalled when a rep for Big
Blue claimed that the S/38 was a computer designed by computers.  
(Noone (but Dorothy) want's to pull back the curtain to see the "true"

Now this same person told me that if I had an attached PC, (now at this
time we are talking XT) the S/38 would detect and use the available CPU
and disk space, all 10mb of it!  I was young then, I thought: "holy
cycles hardwareman. You're my hero!" <g>

Then we begged for CPF V2 :( Heads rolled, blood spilled. It wasn't
pretty.  Sort of reminds me of the B10.

Tell me the B10 wasn't designed by a S/38 as a cruel joke. <g>

"System Support Products, Inc." wrote:
> Booth,
>     I don't know about the early 70's, but the System/34 SSP was
> written on a mainframe in SPL, which looks like a macro language that
> generated S/34 assembler.  Of course, the resulting assembler code
> was also complied on the mainframe.
>     The System/38 microfiche I have show that a language named PL/MI
> was used, which generated S/38 MI.  I'm not sure if this was a true
> compiler, or a macro processor.  This work was done on a mainframe as
> well.
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].