Gerard Schildberger <[email protected]> writes: > Plus, VS/1 also had HASP integrated into it (sometimes > referred to it JES nothing). It also was aware if it > was running under VM/CP and wouldn't bother clearing > storage at IPL time, nor try to figure out the "real" > storage size, as it just simply did a DIAGnose > instruction (in problem state) and ask CP what the > storage size was. If it was exactly 16M, VS/1 disabled > virtual paging and let VM/CP do all the heavy lifting. > Also (I forget the option, maybe PAGEX), if VS/1 got a > page fault, instead of putting the whole of the VS/1 > system into a wait state (waiting for the page to be > paged in), VS/1 was still dispatched and VS/1 knew that > it could dispatch another partition or some other > process (these features where called VS/1 handshaking > and had to be enabled with a directory option). > Also, most system programmers wrote a printer/punch > separator program to spool the output to the job's > submitter, allowing the output to be placed in a CMS > user's reader (which can be read and then edited, and > printed if they wished. > > With VS/1 having 16 meg, I made most of VS/1's I/O > routines + open/close (and DIDOCS) resident, and VS/1 > under VM ran about three times faster than native VS/1.
in the wake of future system imploding http://www.garlic.com/~lynn/submain.html#futuresys there was mad rush to get stuff back into 370 product pipelines. I got sucked into helping Endicott with ecps for 138/148 (followon to 135/145) old post http://www.garlic.com/~lynn/94.html#21 370 ECPS VM microcode assist this went along with vs/1 handshaking performance increase. I also got sucked into (off&on for a year) going around to different countries helping present the business case for 138/148 to business forecasters. Endicott also tried to have vm370 shipped from the factory as part of every machine (sort of like modern day LPAR). However, at the same time POK/MVS was convincing corporate to killoff vm370, shutdown the product group and transfer all the people to POK as part of MVS/XA development. Endicott managed to save the vm370 product mission (had to reconsitute a development group from scratch) ... but prevail in having vm370 shipped as part of every machine from the factory. note the following to 138/148 ... was 4331/4341 and had the endicott followon architecture, "e-architecture" (sort of endicott's equivalent to POK's 370/xa architecture). E-architecture was a little like vs/1 running in virtual machine under vm370 with vm370 handling lots of stuff ... but not quite ... it is where "VSE" originated. one of the interesting business things learned ... was that US was dividied up in regions ... a little like world trade countries. However non-US countries would make a forecast and place an order for that many machines from some factory (and "pay" for them) ... and the machines would be shipped to that country ... and the countries were then responsible for selling those boxes. As a result world trade business forecast people had their jobs on the line when making forecasts. Forecast by US regions carried no such obligations ... business forecasters tended to make a forecast based on internal political winds. US forecasters effectively would say it made no difference what features a product had ... they would forecast whatever they were expected to forecast. Forecasters in world trade were completely different ... they were extremely sensitive to box features and competitive analysis how a box compared point-by-point with the competition. past posts in this thread; http://www.garlic.com/~lynn/2014d.html#54 Difference between MVS and z / OS systems http://www.garlic.com/~lynn/2014d.html#55 Difference between MVS and z / OS systems http://www.garlic.com/~lynn/2014d.html#56 Difference between MVS and z / OS systems http://www.garlic.com/~lynn/2014d.html#57 Difference between MVS and z / OS systems http://www.garlic.com/~lynn/2014d.html#59 Difference between MVS and z / OS systems http://www.garlic.com/~lynn/2014d.html#60 Difference between MVS and z / OS systems http://www.garlic.com/~lynn/2014d.html#61 Difference between MVS and z / OS systems http://www.garlic.com/~lynn/2014d.html#62 Difference between MVS and z / OS systems http://www.garlic.com/~lynn/2014d.html#63 Difference between MVS and z / OS 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
