Gerard Schildberger <[email protected]> writes: > I would'nt bemoan it. I tried using CMS under TSO (or under MVS, I > don't remember), but the response time was lousy (actually, bad > lousy) and the functionality wasn't there. Too many restrictions. > > The same thing kinda happened when the MVS folks said they could support > PROFS (Office Vision) better under MVS/TSO than VM/CMS. Boy, was that > painful to watch. They got it running for a few dozen users, but when > they tried to scale it up to 8,500 (logged on) users, it was choke city. > Never even came close getting that many UIDs logged on. I remember when > OS/VS2 would crash when getting close to 512 address spaces. Does > anybody know when that threshold was lifted? Or is there a new > threshold? > We had half of an Amdahl V7 (I think that was model) running VM with > over 10,400 logged on users/SVMs. The average was at least 9k. The > other half of the Amdahl were three more VMs, each had a goodly-sized > PROFs system, not to mention PVM (Pass-thru) to the whole company, as > well as hosting all the RSCS/net traffic. > ________________________________________________ Gerard Schildberger
re: http://www.garlic.com/~lynn/2014.html#1 Application development paradigms [was: RE: Learning Rexx] http://www.garlic.com/~lynn/2014.html#2 Application development paradigms [was: RE: Learning Rexx] http://www.garlic.com/~lynn/2014.html#4 Application development paradigms [was: RE: Learning Rexx] the 23jun1969 unbundle announcement started charging for application software (they managed to make the case that operating system/kernel software would still be free), SE services, and other stuff ... some past posts http://www.garlic.com/~lynn/submain.html#unbundle they had a issue about hands-on training for new SEs ... which previously had occurred as part of teams at the customer accout (couldn't figure out how not to charge for new SEs if they were on site) ... and came up with providing running operating systems in cp67 virtual machines at branch offices ... i.e. HONE system (hands-on network environment) ... some past posts http://www.garlic.com/~lynn/subtopic.html#hone the cambridge science center ... some past posts http://www.garlic.com/~lynn/subtopic.html#545tech had also ported apl\360 to cp67/cms for cms\apl ... mostly required eliminating unnecessary stuff ... like its internal multi-tasking and swapping (to avoid high overhead os/360 services) ... recent discussion http://www.garlic.com/~lynn/2013o.html#54 Curiosity: TCB mapping macro name - why IKJTCB? but its storage management was oriented to 16kbyte workspaces that were swapped as single unit ... which had to be redone for large virtual memory, demand paged environment ... as well as adding API for CMS system services (combination allowing implementation of large real world applications). The HONE group then started deploying apl-based sales&marketing support applications also on HONE ... which came to dominate all HONE activity and the virtual guest operation use withered away. The palo alto science center then did the apl\cms for vm370/cms ... as well as the 370/145 apl microcode assist. As previously mentioned they had also done the 5100 apl work http://www.garlic.com/~lynn/2013o.html#82 One day, a computer will fit on a desk (1974) - YouTube in the mid-70s, the US HONE datacenters were consolidated in a bldg across the back parking lot from the palo alto science center (later a new bldg. went next door for facebook ... before they bought and moved into the old sun campus). For the heavy computation APL workload, machines were large mainframe SMP configured in loosely-coupled operation ... with single-system-image load-balancing and availability fallover (largest single-system-image operation in the world at the time). The single-system-image was then expanded to cover a 2nd datacenter in dallas and then a 3rd datacenter in boulder. Note that this support didn't appear in the customer product until a couple yrs ago: http://www.garlic.com/~lynn/2009p.html#43 From The Annals of Release No Software Before Its Time http://www.garlic.com/~lynn/2009p.html#46 From The Annals of Release No Software Before Its Time HONE was one of my long-time enhanced operating system customers from original cp67 systems ... even in the early days, they asked me to assist with various installations as HONE clones started popping up around the world. Old email reference to csc/vm http://www.garlic.com/~lynn/2006w.html#email750102 http://www.garlic.com/~lynn/2006w.html#email750430 Pretty much from mid-70s through the 80s, there was re-occurring case of a branch manager being promoted to head of business group that contained HONE and be horrified to find that it ran on vm370 (not MVS). He would then direct the HONE group to move HONE to MVS ... which would take nearly all the HONE resources for 12m-18m ... until it was proven to not be possible ... and then things would settle down for a couple months until they got the next new executive and the cycle would repeat. In the mid-80s, it appeared that somebody decided it was my fault that HONE couldn't move to MVS ... that if HONE was first moved to an unenhanced vm370 system ... then service would deteriate to a level where it would be much easier to move to a MVS system (assumption that the dispartiy between MVS and VM370 would be much less if it wasn't one of my enhanced systems). -- 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
