• Subject: RE: AS/400 History
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Thu, 9 Jul 1998 17:24:02 -0400
  • Organization: commsoft

On Thursday, July 09, 1998 9:31 AM, Al Barsa, Jr. [SMTP:barsa2@ibm.net] 
wrote:
> At 07:03 PM 7/8/98 -0500, you wrote:
> >I think it was System/3 and 36, then System 38.  The Sys/38 had
> > S36 emulation from almost day one.  How could it emulate a
> >machine that didn't already exist?
> >
> The correct order was S/3, S/32, S/34, S/38 and AS/400.
>
> The System/38 never had S/36E.  This notion did not start until the
> AS/400
> was announced.

All this talk about old machines made my fingers relapse 10 years:  I just 
tried to use option 8 to edit a source member a few minutes ago!  I can 
remember how hard it was to re-train my fingers from the /38 displays to 
their /400 counterparts.  There was a time when I actually had to work on 
a S/3 mod 15 console, 3277-2 display attached to the S.3 (CCP), S/38 
console (64 columns?!), 5251-11 display attached to the /38, 3741-1 (and 
2) data entry and a 3196-A1 display attached to a S/34 and S/36 via a 
Black Box twinax switch.  All in the same machine room.  What a mess. 
 It's much nicer today that we can use a single, customisable PC keyboard 
layout to talk to multiple machines.

Buck Calabro
Commsoft, Albany, NY
mailto:mcalabro@commsoft.net

+---
| 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-2019 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].