And just this morning I had been wondering about those who have contributed to this thread, wondering how they could remember so much detail (even if some memory had a few parity checks). Thus, how much truly important personal information had been paged out of their real memory (perhaps to paper tape?), being forever lost to permit these technical details to remain? :-)
Obviously, over the years Lynn has kept more records than a radio station (oops: wrong media -- and now: wrong era). Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Schuh, Richard" <rsc...@visa.com> Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> 05/29/2009 09:10 AM Please respond to "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject Re: IBM 1401 Thanks, Lynn. We knew that we could count on you for the true story. :-) Those of us who have been around since the 1401 days and who have to rely on our memories sometimes mis-remember. Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Anne & Lynn Wheeler > Sent: Thursday, May 28, 2009 7:41 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: IBM 1401 > > rschuh wrote: > > The smaller systems, the 360-20 and 360-30 had a 1401 > emulator mode. It was= > > a h/w or mc based feature. I don't know whether larger > machines had > > it. Th= ere was also a 1410 emulator mode on the -40. I do > not know of > > any 1401 sup= port that ran under DOS, but my DOS experience is > > miniscule.=20 > > 360/30 had 1401 microcode emulation ... actually 360/30 front > panel switch that selected 360 microcode "emulation" (since > 360 was implemented as microcode on > 360/30) and 1401 microcode "emulation" > > recent stories in ibm-main mailing list about univ. getting > 360/30 to replace > 1401 (in staged processs of replacing 709/1401 combo with > 360/67 which was suppose to run with tss/360). > http://www.garlic.com/~lynn/2009h.html#12 IBM Mainframe: 50 > Years of Big Iron Innovation > http://www.garlic.com/~lynn/2009h.html#41 Book on Poughkeepsie > > 709 ran ibsys, tape->tape, a lot of fortran student jobs. > 1401 was front-end "spooling" > handling card reader-> tape & tape->printer/punch for the 709 > ... with tapes being manually moved from 1401 tapes and 709 tapes. > > Even tho the 1401 "MPIO" program ran perfectly fine on 360/30 > in 1401 emulation mode (switch to emulation mode and boot > MPIO from 2504 reader, effectively same as if running real > 1401) ... I got a student job to re-implement it in 360 ... > I got to design my own monitor, interrupt handling, device > drivers, storage management, console interface, etc. > Eventually was 2000 card program with assembler directive > that would either generate a "stand-alone" program or version > that ran under os/360. Stand-alone version took approx. 30 > minutes to assemble ... version that would run under os/360 > took nearly an hour to assemble since it took approx. five > minutes elapsed time per DCB macro. > > The univ. eventually got a 360/67 ... but since tss/360 > wasn't ready, it spent nearly all its time running os/360 as > 360/65. 360/65 (and 360/67) had 709x microcode emulation > support (as opposed to 1401 emulation available on lower-end 360s). > > Last week of January 1968, three people from the science > center ... some past posts > http://www.garlic.com/~lynn/subtopic.html#545tech > > came out to the univ. to install (virtual machine) cp67. at > the time, cp67 wasn't really up to the univ. os/360 > production workload ... but I got to play with it quite a bit > on weekends. some discussion detailed in these posts: > http://www.garlic.com/~lynn/2009h.html#47 Book on Poughkeepsie > http://www.garlic.com/~lynn/2009h.html#48 Book on Poughkeepsie > > misc. other recent related posts in ibm-main mailing list thread > http://www.garlic.com/~lynn/2009h.html#14 IBM Mainframe: 50 > Years of Big Iron Innovation > http://www.garlic.com/~lynn/2009h.html#42 Book on Poughkeepsie > http://www.garlic.com/~lynn/2009h.html#44 Book on Poughkeepsie > > > 360/30 functional characteristics has reference to > 1401/1440/1460 compatibiilty feature (GA24-3255) > http://www.bitsavers.org/pdf/ibm/360/funcChar/GA24-3231-7_360- > 30_funcChar.pdf > > 1401 simulator for os/360 contributed program: > http://www.bitsavers.org/pdf/ibm/360/360D-11.1.019_1401simCorr > _Sep69.pdf > > it might not have been all the difficult to port above to CMS??? > > 1401/1440/1460 Emulator Programs (under dos/360) > http://www.bitsavers.org/pdf/ibm/360/GC27-6940-4_360_1401emul.pdf > > 360/65 functional characteristics > http://www.bitsavers.org/pdf/ibm/360/funcChar/A22-6884-3_360-6 > 5_funcChar.pdf > 360/67 functional characteristics > http://www.bitsavers.org/pdf/ibm/360/funcChar/A27-2719-0_360-6 > 7_funcChar.pdf > > lists optional feature: 709/7040/7044/7090/7094/7094II Compatibility > > single processor 360/67 was nearly identical to single > processor 360/65 except with addition to virtual address > translation hardware. > > > > > > -- > 40+yrs virtualization experience (since Jan68), online at home since > 40+Mar1970 > The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
