[email protected] (Mike Myers) writes: > Lynn: > > I'm quite familiar with that project. Three others and I actually > implemented a prototype which let a TSO user issue the command CMS > which would obtain a block of storage in the TSO address space and > load and run the CMS kernel using SIE. Attempts to perform file I/O > would interrupt SIE and execute code which implemented the CMS file > system and all needed file functions in a VSAM data set, using CI file > I/O. A later design would use the VSAM actual block processor, as > opposed to CI file I/O. That file system implementation was my > contribution to the project. > > Two of us were assigned as technical team leaders for the intended > product development. We were staffing our teams when the project was > killed.
re: http://www.garlic.com/~lynn/2012o.html#30 Regarding Time Sharing http://www.garlic.com/~lynn/2012o.html#31 Regarding Time Sharing http://www.garlic.com/~lynn/2012o.html#34 Regarding Time Sharing http://www.garlic.com/~lynn/2012o.html#35 Regarding Time Sharing http://www.garlic.com/~lynn/2012o.html#36 Regarding Time Sharing for other drift ... given SIE was for vmtool, internal development and virtual guests ... the 3081 implementation was extremely heavy-weight ... executing SIE could consume more elapsed time ... than typical CMS execution ... including 3081 microcode store was extremely constrained ... and the SIE microcode might actually have to be "paged in". old email about how 3090 was doing a lot of work fixing some of the enormous short-comings of 3081 SIE: http://www.garlic.com/~lynn/2006j.html#email810630 aka the 3033 was kicked off in parallel with 3081 ... 3033 was real q&d started out mapping 168-3 logic to some other FS chip technology that was 20% faster ... but also had 10 times the circuits per chip. Some logic redesign doing more on-chip ... got 3033 up to 50% faster than 168-3. when 3033 was out-the-door, that group then starts on 3090. 3090 eventually announces 12Feb1985 http://www-03.ibm.com/ibm/history/exhibits/mainframe/mainframe_PP3090.html and other old email about 3090 service processor group (pair of 4361s running highly modified version of vm370 release 6) wanting to use my DUMPRX debug tool (I had originally thought it would be released to customers ... especially after it was in use my nearly every internal datacenter as well as customer support PSRs): http://www.garlic.com/~lynn/2010e.html#email861031 http://www.garlic.com/~lynn/2010e.html#email861223 the person writing the above didn't realize that I had helped the manager that kicked off the vm370 service processor effort several years earlier ... which happened to also be in the middle of the "tandem memo" days ... aka I had been blaimed for online computer conferencing on the internal network in the late 70s and early 80s (folklore is that when executive committee were told about online computer conferencing and the internal network, 5of6 wanted to fire me). misc. past posts mentioning dumprx http://www.garlic.com/~lynn/submain.html#dumprx other issues were that 3081 was quick&dirty effort (in parallel with 3033) kicked off after future system failure ... using some warmed over FS technology. past posts mentioning FS http://www.garlic.com/~lynn/submain.html#futuresys more detailed discussion of 3081 being warmed over FS http://www.jfsowa.com/computer/memo125.htm for something similar, but different, as undergraduate in the 60s, I modified MVT R18/HASP ... removing 2780 support (to reduce storage footprint) and put in 2741&tty/ascii terminal support along with editor that implemented CMS edit syntax (no way for straight port since the programming enivornments were so different) ... which I always much preferred to TSO (assuming having to deal with os/360 and not being able to use real cms). misc. posts mentioning HASP, JES2, NJI, etc http://www.garlic.com/~lynn/submain.html#hasp -- 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
