Tss was implemented at Computer Scieces Corp -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Anne & Lynn Wheeler Sent: Friday, March 09, 2007 11:17 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: IBM S/360 series operating systems history
Rick Fochtman wrote: > MVT and MFT never knew anything about DAT boxen. IIRC, the only 360 > with > a DAT box was the 67, mainly for running CP67/CMS, the predecessor to > VM. The early 370 machines, 155 and 165 had no DAT box but they could be > upgraded to 155-II and 165-II by adding a DAT box, along with some other > features. recent post in this thread: http://www.garlic.com/~lynn/2007f.html#6 IBM S/360 series operating systems history DAT Hardware for 165-II was especially big hit ... there was bunch of stuff in 370 virtual memory architecture (i.e. "redbook" was cms script file, depending on the options set, it either produced the full architecture redbook or the subset 370 principle of operations). at one point there was an escalation meeting where the 165 engineers proposed dropping a bunch of stuff from the DAT architecture on the grounds that they could get virtual memory hardware out six months earlier if they didn't have to do all the extra stuff. It was eventually agreed to ... and then all the other products that already had full 370 virtual memory architecture implemented ... had to go back and remove all the stuff dropped to help 165 improve their delivery schedule. 360/67 was originally for something called tss/360 ... which never really got out of development ... there were all these release 0.xx something in customer shops ... but the performance was really horrible (among other issues). cp67/cms started as bootlegged project at the cambridge science center http://www.garlic.com/~lynn/subtopic.html#545tech and eventually found customer installation at a lot of places that had orderd 360/67 for tss/360. another project that saw some amount of installations was MTS (michigan terminal system) done at UofM ... that made use of the 360/67 dat box. The morph from cp67 to vm370 had barely made it into customer installations and POK discovered that it had enormous problem with MVS/XA development schedule. POK was able to convince corporate to kill off the vm370 product and have all of the vm370/cms development group transferred to POK to help with MVS/XA development. At the last minute, Endicott managed to salvage a little of the vm370 product development mission and acquire a small part of the development staff ... in order to keep the product going. for a lot more on the early 360/67 period, including science center implementing early virtual machine cp40 & cms on a custom modified 360/40 (with virtual memory hardware added) before 360/67 machines became available ... see Melinda's history http://www.princeton.edu/~melinda ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
