[email protected] (Phil Smith) writes: > Today's random wondering: how many operating systems can folks remember > having run on S/360 and descendants? I can think of: > > OS/360 (including MFT, MVT, MVS, up thru z/OS, including MSP and VOS3) > VM (CP/40 up thru z/VM) > DOS (or did it start as TOS? Not my turf! up thru z/VSE) > ACP (up thru z/TPF) > TSS > MUMPS > MUSIC > PICK > AIX > Linux, of course > Solaris, almost > ORVYL? WYLBUR? I think ORVYL was the OS and WYLBUR was the user > environment - sort of the CP-CMS or z/OS-TSO relationship, but canna > remember for sure; someone here will know > VICOM > > What others? No credit for things like DDR or ICKDSF, which, while > IPLable, aren't really "OSes" in any kind of real sense!
trivia: there is card based BPS for 360 ... and science center used BPS loader to generate the CP/40 & CP/67 kernel. Cambridge Science Center thought they would get the IBM responsibility for dealing with MIT Multics (some of the CTSS/7090 people had gone to 5th flr to do Multics and others went to the science center on the 4th flr) http://www.garlic.com/~lynn/subtopic.html#545tech This CTSS wiki entry has longer list of IBM operating systems (not just but including 360) https://en.wikipedia.org/wiki/Compatible_Time-Sharing_System The TSS group didn't win the Multics bid. TSS/360 was the official operating system for virtual memory version of 360/65, the 360/67 and was sold to a lot of customers. The science center went ahead and did virtual machine CP/40 for a 360/40 with special hardware modifications to support virtual memory. Then when standard 360/67 with virtual memory becomes available, CP/40 morphs into CP/67. TSS/360 has very difficult time becoming production quality and is decommitted. Many customers reverted to running 360/67 in 360/65 with os/360. Along the way stanford does (virtual memory) ORVYL for 360/67 (& WYLBUR is text editor) https://en.wikipedia.org/wiki/ORVYL_and_WYLBUR http://www.slac.stanford.edu/spires/explain/manuals/ORVMAN.HTML https://web.stanford.edu/dept/its/support/wylorv/ Univ. of Michigan does MTS for 360/67. UM ports MTS to 370 and it is installed at a number of universities ... and Amdahl installations. https://en.wikipedia.org/wiki/Michigan_Terminal_System http://archive.michigan-terminal-system.org/ Recent post about AIX, MACH (unix-like from CMU) and LOCUS (unix-like from UCLA) http://www.garlic.com/~lynn/2017b.html#46 The ICL 2900 http://www.garlic.com/~lynn/2017d.html#41 What are mainframes Palo Alto ports UCLA LOCUS to 370 and 386 for AIX/370 and AIX/386 https://en.wikipedia.org/wiki/LOCUS_(operating_system) recent posts mentioning the poor MVT storage management is motivation for moving all of 370 to virtual memory http://www.garlic.com/~lynn/2017.html#90 The ICL 2900 http://www.garlic.com/~lynn/2017b.html#8 BSAM vs QSAM http://www.garlic.com/~lynn/2017c.html#80 Great mainframe history(?) http://www.garlic.com/~lynn/2017c.html#81 GREAT presentation on the history of the mainframe trivia: Boeing Huntsville had gotten a smp 2-processor 360/67 to run with tss/360 2250 cad design applications ... but has to revert to running as two 360/65s and 2250 cad applications. MVT storage management problems especially show up with long running applications (one reason why CICS got all the storage it could at startup and did its own management) and it caused lots of problem for the 2250 cad programs. Boeing Hunstville does special modifications to os/360 MVT to support virtual memory running in 360/67 mode. This doesn't do any paging ... but purely reorganizes memory for contiguous allocation to compensate for some of the MVT storage management problems. As undergraduate at the univ. I'm hired fulltime to be responsible for OS/360 production systems. The univ. library gets ONR grant to do online catalog. Some of the money goes to 2321 datacell. The online catalog is also selected as beta test site for the original CICS product ... and I have to shoot a lot of bugs ... some past posts http://www.garlic.com/~lynn/submain.html#cics Boeing then hires me away to help with the formation of Boeing Computer Services (consolidate all dataprocessing in independent business unit to better monetize the investment, including offering services to non-Boeing entities). The Boeing Huntsville machine is moved to Seattle. more trivia: CERN does a comparison of VM/CMS and VS2/TSO which is presented at SHARE. Copies of the comparsion circulated inside of IBM are stamped "IBM - Confidential Restricted" ... basically on a need-to-know basis only .... because what CERN found doesn't go along with the official corporate party line (and tried to minimize the exposure to IBM employees). -- virtualization experience starting Jan1968, online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
