| PLEX86 | ||
winscape 2297recent thread on the subject in comp.arch. when we were having arguments about 3274 not providing interactive support ... the 3274 group effectively came back and said that 3274 wasn't designed to provide interactive support ... its design point was for data entry support ... being better than keypunches ... and the TSO people effectively came down on the side of the 3274 ... in effect that TSO was never designed to provide interactive support ... it was designed to provide data entry support. misc. other recent posts mentioning 3274 for 360s, supposedly the official time-sharing product was tss-360 for 360-67 (360-65 with the additional of virtual memory support). it was having all sort of difficulties ... and somewhat as a result, univ. of mich came out with MTS (michigan terminal system) for 360-67 and science center did cp67 virtual machine timesharing system for 360-67. note that multics was on the 5th floor and the science center was on the 4th floor and both multics and cp67 have common heritage w-ctss. I don't know of any from multics ... but there were two time-sharing service bureaus in the 60s that spun off to provide commercial time-sharing service. a little later tymshare was also using it to provide commercial time-sharing services ... misc. past postings referencing time-sharing services random drift .. recent mention of tymshare, interactive computing and hyperlinks in comp.databases.theory winscape 2298 Fascinating. Thanks. The standard joke(s) about TSO make more sense now. When I was using it (mostly for preparing and submitting batch jobs and checking their output), it seemed to me... -- winscape 2299 No, not even Redmondware ist that bad. This three step list is just the more escalation order...
|
||||
Alt Folklore Computers from Newsgroups The #1 Usenet Provider on the Internet
|
||||