Re: LPARs: More or Less?
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. re: http://www.garlic.com/~lynn/2010e.html#75 LPARs: More or Less? basically SIE greatly expanded the architecture definition for virtual machine mode ... as addition/alternative to real machine mode ... aka principle of operations defines a lot of stuff about how things operate in real machine mode ... virtual machine mode makes various changes ... like what are the rules for supervisor problem state when running in virtual machine mode; it greatly increased performance of running in virtual machine mode (compared to full software simulation) ... modulo 3081 choosing to have the service processor page the SIE microcode on 3310 FBA device ... recent ref http://www.garlic.com/~lynn/2010e.html#34 Need tool to zap core now one of the big guest performance hits to vm370 was transition from svs to mvs ... because the number of times that MVS changed CR1 exploded (compared to svs) ... requiring vm370 to flush the shadow page tables each time (virtual machine changed its virtual cr1). now one of the things that could be done in a SIE scenario is to change the operation of TLB miss/reload in virtual machine mode ... so that hardware performed the double lookup on TLB miss ... eliminating the requirement for having shadow tables (instead of having to maintain the shadow table information ... which then is significantly amount of overhead in flush scenario ... whether explicit via virtual PTLB or implicit by change in virtual CR1 value). As SIE began to blanket nearly ever aspect of machine operation ... with the virtual machine flavor ... it greatly simplified the introduction of LPARs. there use to be some SHARE thing about the greatly increasing MVS bloat ... one was scenario about creeping processor bloat ... possibility of waking up one day and MVS was consuming all processor cycles with none left for applications. This was somewhat the capture ratio scenario where the amount of processor cycles even being accounted for, falling below 50%. The san jose plant site highlighted a 70% capture ratio of MVS system dedicated to apl ... but the apl subsystem was doing nearly everything possible to avoid using any MVS system services as method of improving thruput and performance. recent capture ratio mention http://www.garlic.com/~lynn/2010e.html#33 SHAREWARE at Its Finest The creeping bloat of common segment area size was similar ... threatening to totally consume the remaining 16mbyte virtual address space ... leaving nothing for applications to run. The dual-address space introduction in 3033 was an attempt to at least slow down the creeping common segment size bloat (threatening to totally consume all available virtual address space). -- 42yrs virtualization experience (since Jan68), online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Reminds me of arguments I heard in the 1980s like, I can do more work on a 3081 running two VS1 machines under VM than you can on your 3084-Q running under MVS. Odd not to hear anything in this thread about things like virtual storage. I have encountered systems with an ECSA requirement so large that no number of physical processors can mitigate it. You could solve the problem by moving half the work to a second box, or move half the work onto a second LPAR on the same box and share the physical processors ~50-50. Which sounds more economical? The notion that the point is moot because basic mode is no longer available doesn't sit right with me. The option to run a single OS image per box is still available, and the difference between a single LPAR and a basic mode system is vanishingly small. IIRC, Linda August of IBM quantified it in a white paper in 2006. The real kicker is that, in spite of LPAR switching overhead, it is possible to see capacity GAINS through the use of logical partitioning. In the interest of time, I refer the interested reader to The Effects of MP Serialization on Logical Partitioning Capacity presented by Bob Ellworth, Amdahl Consultant Systems Engineering, SHARE 86 - session 2547. In this paper Bob introduced the world to the concept of underhead in 1996. The advantage of logical partitioning as opposed to physical partitioning (as on our old 3033-AP) from a practical standpoint needs no explanation to this audience. Those issues aside, the case for LPARing may be less compelling than it was prior to the advent of parallel sysplex. Nevertheless, (no disrespect to Mr. Henke) the proof of the case for-or-against can be made empirically with evidence that already exists. db -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of George Henke Sent: Friday, March 05, 2010 4:50 PM To: IBM-MAIN@bama.ua.edu Subject: Re: LPARs: More or Less? Gentlemen, I am indeed very grateful to you all and thank you all. There is, indeed, compelling evidence supporting the case for fewer and even no LPARs but, unfortunately, it is proprietary and cannot be presented. I know that all sounds a little too convenient, but it is true. But thank you all and rest assured I have, indeed, read and learned and appreciate very much all that you all have written and said. Please, no hard feelings. Thank you. On Fri, Mar 5, 2010 at 2:37 PM, Ted MacNEIL eamacn...@yahoo.ca wrote: I'm still kind of curious what exactly you mean by: - Performance: wasted CPU cycles especially for handshaking between LPARs doing shared I/O So am I. I haven't seen these issues since the early days of MDF and PR/SM in the 1980's. I have thoughts on what you mean by these kinds of things, but I am reserving judgement. I'm not. This sounds like a diatribe against something that has matured in the last 25 years. Rather than say it's bad because I say it's bad, present some evidence. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
From: Dave Barry dba...@ups.com To: IBM-MAIN@bama.ua.edu Sent: Wed, March 10, 2010 2:22:06 PM Subject: Re: LPARs: More or Less? Reminds me of arguments I heard in the 1980s like, I can do more work on a 3081 running two VS1 machines under VM than you can on your 3084-Q running under MVS. ---SNIP__ I can not imagine this argument could ever be given with VS1. With SAMe MVS was warp:) fast. Seriously I did a conversion from VS1 to MVS and the work was done in 3 hours less than VS1. This mind you was on a 4341 with 4 meg of memory (later upgraded to 8). Our production crew couldn't believe how fast MVS was over VS1 . They had 5 or 5 people going over every sysout to see what the difference was (I mean output). They just could not find anything and everything balanced to the penny and options traded. The jobs literally flew pass the operators and they could not keep up with the job flow. The other item that our IBM CE loved was that we chose random tape assignment. The 380 drive that used to break down once a night was not used any where close to the same amount. The operators hated it as they used to be able to figure out in what order the drives were going to be mounted and pre mount them. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On Monday 08 March 2010, Stephen Y Odo wrote: I've been trying to get Linux onto our z890 (even have CENTOS running in an LPAR as a proof-of-concept) What version of CentOS, and where did you find an installation image? I looked around for one a year or so ago, but couldn't find one that wasn't years out of date. iirc, the CentOS folks used to maintain regular builds for 390/System z, but seem to have stopped some time ago. I guess there aren't any mainframers active in the CentOS project anymore. (Sad to say, that sort of thing is symptomatic of moribundity in a platform.) but our management has decreed that all future development will be Solaris/SPARC or Linux/Intel. Why no Solaris/Intel option? -- Bob Woodside Woodsway Consulting, Inc. http://www.woodsway.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On 6 March 2010 20:40, Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net wrote: on 03/05/2010 at 04:24 PM, Ted MacNEIL eamacn...@yahoo.ca said: Outside of IBM, I've only met two people with VM and MVS skills. This is in the Greater Toronto Area, over the last 30 years. To me, that's rare. Very well; I retract my original response. Instead, I'll state that it's not at all rare outside of the Greater Toronto Metropolitan Area. I'm not, however, ruling out the possibility that there are lots of people in toronto with both skill sets that you simply haven't met. Ted, you're full of it. I don't believe we've ever met, but I am one Toronto person with VM and MVS skills both going back 30+ years, and both current today. Certainly the number of large MVS shops running under VM has dropped, but they still exist. Back in the 1980s, at the Canada VM Users Group (CVMUG) meetings, about half the attendees were large MVS/VM shops, and the other half were smaller VSE/VM installations. (And somewhere around that time the VM-only shops appeared, running PROFS and related office automation and Information Centre stuff.) In any case, there were lots of people at these meetings, and of course at SHARE and on VMSHARE, with strong skills in both OSs, and in particular in running MVS under VM. Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On 6 March 2010 16:38, Anne Lynn Wheeler l...@garlic.com wrote: There was a separate performance issue going from virtual MVT guests to virtual SVS/MVS guests ... since VM started out simulating the TLB (hardware look aside buffer implementing virtual memory) with shadow page tables. Mmmm... I'm not sure the analogy is quite right. Shadow tables are not merely a performance optimization like the TLB; they are a requirement for running a DAT-on OS in a VM that is implemented without a SIE-like function. The management of the entries in the shadow page tables with software was enormously slower than the hardware overhead involved in managing TLB entries. I'm still not convinced they are related. Hardware-level TLB management would still be there for the shadow tables. In the early days where the only TLB invalidating instruction was PTLB, which clobbered the whole thing, the trick would presumably lie in avoiding that instruction like the plague. But you know all this... Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Ted, you're full of it. I don't believe we've ever met, but I am one Toronto person with VM and MVS skills both going back 30+ years, and both current today. If you say so. But, your attack doesn't change the fact that I've only met two, in the GTA, since 1981. I DID say, in my experience, if there are more, I've not met them. And, until 2003, I've worked in VM MVS shops for years. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. t...@harminc.net (Tony Harminc) writes: I'm still not convinced they are related. Hardware-level TLB management would still be there for the shadow tables. In the early days where the only TLB invalidating instruction was PTLB, which clobbered the whole thing, the trick would presumably lie in avoiding that instruction like the plague. recent threads mentioning shadow tables http://www.garlic.com/~lynn/2010e.html#1 LPARs: More or Less? http://www.garlic.com/~lynn/2010e.html#2 LPARs: More or Less? http://www.garlic.com/~lynn/2010e.html#28 What was old is new again (water chilled) The TLB rules followed by shadow table operation also did implicit invalidation everytime address space pointer changed. the shadow tables operation followed the same rules as for TLB. PTLB, ISTO, ISTE, IPTE were all instructions in the original 370 virtual memory architecture. When 370/165 hardware group ran into problems with the virtual memory hardware retrofit ... and wanted to drop several features in order to buy back six months in schedule ... ISTO, ISTE, and IPTE were part of the things from the base architrecture that were dropped (leaving only PTLB ... i.e. everytime any invalidation occured, everything got invalidated). Also, original cp67 and vm370 shadow table only had a single STO stack ... this is analogous to the 360/67 and 370/145 TLB ... where everytime there was control register address space pointer changed (CR0 in 360/67 and CR1 in 370/145) ... there was an implicit TLB purge (aka all TLB entries implicitly belonged to same/single address space). The corresponding vm370 implementation was that all shadow table entries were purged ... anytime there was a CR0/CR1 change. The 370/168 had seven entry STO-stack ... aka every TLB entry had a 3bit identifier (8 states, invalid, or belonging to one of seven address spaces, 370/145 TLB entries had single bit, either valid or invalid). Loading new CR1 value on 370/168 didn't automatically purge the whole TLB ... it would check if the enw value was one of the already loaded saved values ... and if there was match ... it would continue. If the new address space value loaded into CR1 didn't match a saved value ... it would select one of the seven saved entries to be replaced ... and invalidate/reset all TLB entries that had the matching 3bit ID. VM370 product didn't support multiple shadow tables until the priced kernel addon to VM370 release 5. MVS did extremely frequent change to the CR1 value ... even w/o doing explicit PTLB ... and evertime ... VM had to do the full invalidation of all shadow table entries ... corresponding to the similar implicit operation that went on with 370/145 (not having a multiple entry STO-stack at least up until the priced kernel add-on to vm370 release 5). There was somewhat analogous issue on real 3033 hardware with the introduction of dual-address space mode. The 3033 was effectively the same logic design as 370/168 ... remapped to slightly faster chips ... and as such ... the TLB had the same seven entry STO-stack. When using dual-address space mode ... the increase in number of different address space pointers was overruning the 3033 (seven entry) STO-stack and the frequency of (implicit) TLB entry invalidations went way up ... to the point that dual-address space was running slower than common segment implementation. Dual-address space mode was somewhat a subset retrofit of the 370-xa multiple address spaces. The common segment problem on 370 was MVS kernel was taking half the 16mbyte address space and common segment started out taking only single mbyte segment. The common segment was to address the pointer passing paradigm from MVTSVS days for subsystems ... which had resided in the same address space as the application. With the move to MVS, the subsystems were now in different address space (from the calling applications) and broke the pointer passing API paradigm. The solution was to have common segment that was the same in applications and subsystems. The problem was common segment grew with the subsystems installed and applications using subsystems ... and larger installations had common segment area pushing over five mbytes (threatening to leave only 2mbytes for applications use). Burlington lab was large MVS shop with large chip design fortran applications and a very carefully crafted MVS that held common segment area to one mbyte ... so the applications still had seven mbytes. However, with increases in chip complexity ... it was forcing the fortran applications over seven mbytes ... threatening to convert the whole place to vm/cms ... since the fortran applications under CMS could get very nearly the whole 16mbytes. -- 42yrs virtualization experience (since Jan68), online at home since Mar1970 -- For
Re: LPARs: More or Less? (OT, somewhat)
Okay. We can use only what we see. On the other hand, are there any jobs in Edmonton for a senior Capacity/Performance/DR/Config specialist with almost 30 years in? --Original Message-- From: John Baxter Sender: IBM Mainframe Discussion List To: IBM Mainframe Discussion List ReplyTo: IBM Mainframe Discussion List Sent: Mar 5, 2010 16:16 Subject: Re: LPARs: More or Less? (OT, somewhat) Ah, the good old GTA; come visit Edmonton, Ted. There are a number of ambidextrous sysprogs in our area. (Not to put T.O. down - I lived there during the 60's 70's and loved it.) -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Friday, March 05, 2010 9:25 AM To: IBM-MAIN@bama.ua.edu Subject: Re: LPARs: More or Less? No, I wouldn't call it popular, but I wouldn't call it rare either. I have worked on VM off and on throughout my career. Outside of IBM, I've only met two people with VM and MVS skills. This is in the Greater Toronto Area, over the last 30 years. To me, that's rare. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html The information transmitted is intended only for the addressee and may contain confidential, proprietary and/or privileged material. Any unauthorized review, distribution or other use of or the taking of any action in reliance upon this information is prohibited. If you receive this in error, please contact the sender and delete or destroy this message and any copies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
CentOS on z890 LPAR [was Re: LPARs: More or Less?]
Bob Woodside wrote: On Monday 08 March 2010, Stephen Y Odo wrote: I've been trying to get Linux onto our z890 (even have CENTOS running in an LPAR as a proof-of-concept) What version of CentOS, and where did you find an installation image? I looked around for one a year or so ago, but couldn't find one that wasn't years out of date. iirc, the CentOS folks used to maintain regular builds for 390/System z, but seem to have stopped some time ago. I guess there aren't any mainframers active in the CentOS project anymore. (Sad to say, that sort of thing is symptomatic of moribundity in a platform.) I downloaded the CentOS 4.8 s390x tape install files from their site and built a boot tape on a 3490E cartridge. Used the ICKDSF bootstrap loader I downloaded from somewhere off of the net (sorry, lost my notes so don't know where I found anything ... used Google to find everything including the notes on how to do it ... from the SHARE or Linux/VM web site I think) ... Booted from the tape to run the CentOS installer and now I have a system running. but our management has decreed that all future development will be Solaris/SPARC or Linux/Intel. Why no Solaris/Intel option? Because we've standardized on SPARC ... we have over 100 SPARC boxes of various sizes and flavors in our machine room ... --Stephen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Hi Mike, Nice talking to you again. I don't know whether it was free or just inexpensive and therefore virtually free (no pun intended). One of the university hospitals that has it is Johns Hopkins in Baltimore. They might know. Infact, they have a LINUX under z/VM project going on there. I will check around for you and see if I can find out the IBM program that offers this. On Sat, Mar 6, 2010 at 8:54 PM, Mike Myers m...@mentor-services.com wrote: George: That's interesting to me that you would suggest IBM will give z/VM for free to hospitals. I am presently consulting at a hospital that is moving away from z/OS and moving their primary applications to the mid-range. I would like to get the to look at using the mainframe for Linux, under z/VM. Could you provide me with a link or reference to the IBM program or policy that is proposing this offering? Mike Myers Mentor Services Corporation (919) 341-5210 On 3/5/2010 12:23 PM, George Henke wrote: It wasn't until zLinux popped up that I started working with VM again, which I think is getting more and more common, so the dual skill set ismaking a come back. You're absolutely right, Mark. I know a very large financial company who is doing just that after the project was languishing for 6 years. Also, it should be noted, that IBM offers z/VM virtually for free to hospitals and universities as long as they use it for research. So you will find z/VM and z/OS living happily together at such institutions which is where I installed z/VM 5.4 last November. On Fri, Mar 5, 2010 at 12:13 PM, Mark Zeldenmzel...@flash.net wrote: On Fri, 5 Mar 2010 16:24:51 +, Ted MacNEILeamacn...@yahoo.ca wrote: No, I wouldn't call it popular, but I wouldn't call it rare either. I have worked on VM off and on throughout my career. Outside of IBM, I've only met two people with VM and MVS skills. This is in the Greater Toronto Area, over the last 30 years. To me, that's rare. That is your experience, which is what you are writing about. I will say it is much more rare these days than it was 20 years ago. At least in the Chicago area. There used to be a lot of shops running VM along with MVS (and hence many sysprogs with experience in both) but many of them got rid of VM. The last full time VM I supported was VM/XA but I also worked with VM/ESA and VM/HPO not long after that but there was a full time VM sysprog that really supported those environments when I worked on them. It wasn't until zLinux popped up that I started working with VM again, which I think is getting more and more common, so the dual skill set is making a come back. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
We used to be a VM and MVS shop (so I guess I'm one of those few who have experience with both). We ran VM just to run multiple MVS guests. A couple of those guests were for our Computer Science department to use for teaching purposes so VM was nice (all they had to do was login and IPL -- no need for access to the HMC). As a cost-cutting measure, our management decided to scrap VM in favor of PR/SM and LPARs. And so our students were deprived of access to MVS. MVS is only used for administrative systems now (our financial system is the last application running). I've been trying to get Linux onto our z890 (even have CENTOS running in an LPAR as a proof-of-concept) but our management has decreed that all future development will be Solaris/SPARC or Linux/Intel. No discussion has been or will be entertained about the mainframe in our future -- it is history. If memory serves, we used to have quite a few shops running MVS as guests under VM a long time ago. Many of those shops have migrated or are migrating to Windows or Solaris. A couple have moved to System i (AS/400?). There are very few mainframes left in the islands. --Stephen Mark Zelden wrote: On Fri, 5 Mar 2010 16:24:51 +, Ted MacNEIL eamacn...@yahoo.ca wrote: No, I wouldn't call it popular, but I wouldn't call it rare either. I have worked on VM off and on throughout my career. Outside of IBM, I've only met two people with VM and MVS skills. This is in the Greater Toronto Area, over the last 30 years. To me, that's rare. That is your experience, which is what you are writing about. I will say it is much more rare these days than it was 20 years ago. At least in the Chicago area. There used to be a lot of shops running VM along with MVS (and hence many sysprogs with experience in both) but many of them got rid of VM. The last full time VM I supported was VM/XA but I also worked with VM/ESA and VM/HPO not long after that but there was a full time VM sysprog that really supported those environments when I worked on them. It wasn't until zLinux popped up that I started working with VM again, which I think is getting more and more common, so the dual skill set is making a come back. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
George Henke wrote: Also, it should be noted, that IBM offers z/VM virtually for free to hospitals and universities as long as they use it for research. and that's the rub. why the requirement that it be used ONLY for research? none of the other vendors have such restrictions. that's one of the biggest reasons we're moving off of the mainframe ... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
step...@hawaii.edu (Stephen Y Odo) writes: and that's the rub. why the requirement that it be used ONLY for research? none of the other vendors have such restrictions. that's one of the biggest reasons we're moving off of the mainframe ... telcos faced something similar with dark fiber and NSFNET backone in the 80s ... (tcp/ip is technology basis for modern internet, NSFNET backbone was operational basis for modern internet, and CIX was business basis for modern internet). telcos have large fixed costs expenses ... but recover costs based on useage. all the fiber going into the ground enormously increased capacity ... however w/o signicant reduction in use charges ... people weren't going to use the extra capacity. however, any upfront reduction in the use charges w/o the bandwidth hungry applications ... would result in telcos operating at significant loss for possibly decade (period it would take for the new bandwidth hungry applications to evolve in an environment with drastically reduced fees). the telcos leveraged NSFNET backbone as a commercial-free technology incubator. The NSFNET backbone RFP was awarded for $11.2M ... and was for non-commercial use only. Folklore is that resources put into NSFNET backbone was closer to four times the RFP. The non-commercial use of the NSFNET backbone would limit impact on telco revenue ... but at the same time telcos could provide large amount of extra resources for non-profit educational technology incubator to promote evolution of the bandwidth hungry applications. misc. old email about NSFNET backbone http://www.garlic.com/~lynn/lhwemail.html#nsfnet we had been working with NSF and various institutions leading up to NSFNET backbone effort ... but then weren't allowed to bid on the RFP. The director of NSF attempted to help by writing letter to corporation asking for our help (there were also comments like what we already had running was at least five years ahead of all the NSFNET backbone RFP responses to build something new). Turns out that just aggrevated the internal politics. -- 42yrs virtualization experience (since Jan68), online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Mike Myers wrote: That's interesting to me that you would suggest IBM will give z/VM for free to hospitals. I am presently consulting at a hospital that is moving away from z/OS and moving their primary applications to the mid-range. I would like to get the to look at using the mainframe for Linux, under z/VM. Keep in mind that this is only for RESEARCH use. Using the system to run the hospital is NOT considered supporting research at the hospital. That was the problem we had. We used VM + MVS to run our financials, human resources, and student information systems. Those activities are not qualified as support of research at our University (according to IBM, those are administrative functions). Thus we paid regular price (less 15% academic institution discount). Which made it way too expensive for us. And paved the way for our migration to Solaris (which was FREE whether we used it for academic OR research OR administrative purposes). --Stephen -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
step...@hawaii.edu (Stephen Y Odo) writes: Thus we paid regular price (less 15% academic institution discount). Which made it way too expensive for us. And paved the way for our migration to Solaris (which was FREE whether we used it for academic OR research OR administrative purposes). I vaguely remember in the 60s ... the academic institution discount was 40% ... but that seemed to change with the 23jun69 unbundling announcement (in response to gov. litigation) ... along with starting to charge for application software, SE services, and other stuff. http://www.garlic.com/~lynn/submain.html#unbundle -- 42yrs virtualization experience (since Jan68), online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Is that still true Stephen ?. I hear talk that (in the non-education world) Oracle is now charging for Solaris security fixes. Larry trying to claw back some of his investment maybe. Shane ... On Tue, Mar 9th, 2010 at 8:22 AM, Stephen Y Odo wrote: ... And paved the way for our migration to Solaris (which was FREE whether we used it for academic OR research OR administrative purposes). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
dunno. our licensing hasn't been affected ... yet. --Stephen Shane Ginnane wrote: Is that still true Stephen ?. I hear talk that (in the non-education world) Oracle is now charging for Solaris security fixes. Larry trying to claw back some of his investment maybe. Shane ... On Tue, Mar 9th, 2010 at 8:22 AM, Stephen Y Odo wrote: ... And paved the way for our migration to Solaris (which was FREE whether we used it for academic OR research OR administrative purposes). -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
I used to work with both VM and MVS back in the 90s. Our VM guy at PH Mining went back to programming, so I volunteered to learn VM. We were running VM on our 3081 with VM 4.3 running HPO. We had a whole bunch of things people did with Cadam drawings that they had written CMS execs for. We finally moved VM to its own box, a 4381 at the time. We were able to get rid of it in early 1999, so we didn't have to worry about Y2K for any of its applications. I'm curious. The last release of VM I really worked with was 5.1 - no XP or later stuff. Has it changed much, or are most of the concepts still the same? Eric Bielefeld Sr. Systems Programmer IBM Global Services Division Dubuque, Iowa 414-477-7259 - Original Message - From: Mark Zelden mzel...@flash.net Subject: Re: LPARs: More or Less? On Fri, 5 Mar 2010 16:24:51 +, Ted MacNEIL eamacn...@yahoo.ca wrote: That is your experience, which is what you are writing about. I will say it is much more rare these days than it was 20 years ago. At least in the Chicago area. There used to be a lot of shops running VM along with MVS (and hence many sysprogs with experience in both) but many of them got rid of VM. The last full time VM I supported was VM/XA but I also worked with VM/ESA and VM/HPO not long after that but there was a full time VM sysprog that really supported those environments when I worked on them. It wasn't until zLinux popped up that I started working with VM again, which I think is getting more and more common, so the dual skill set is making a come back. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
VM has changed considerably since HPO 5.1. Long gone are the days of assembling modules to apply service and to add devices (thank god). To the sysprog servicing VM is pretty much two commands (after the service envelope is uploaded). And of course all modern devices can be sensed. Most of the new support now centers around capacity (very large virtual machines) and virtual networking (virtual switch). There is a statement of direction for clustering (not sysplex) and guest migration (moving live machines between VM systems). All of this with the intent of supporting Linux. The motherhood and apple pie concepts of VM haven't changed much since HPO. The line oriented commands, XEDIT, etc On 03/06/2010 07:46 AM, Eric Bielefeld wrote: I'm curious. The last release of VM I really worked with was 5.1 - no XP or later stuff. Has it changed much, or are most of the concepts still the same? Eric Bielefeld Sr. Systems Programmer IBM Global Services Division Dubuque, Iowa 414-477-7259 -- Rich Smrcina Phone: 414-491-6001 http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2010 - Apr 9-13, 2010 Covington, KY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. r...@velocitysoftware.com (Rich Smrcina) writes: Most of the new support now centers around capacity (very large virtual machines) and virtual networking (virtual switch). There is a statement of direction for clustering (not sysplex) and guest migration (moving live machines between VM systems). All of this with the intent of supporting Linux. note that some of the commercial (virtual machine) timesharing service bureaus had done moving live machines between VM systems in the early 70s, it was combination of 7x24 operation and providing services to customers around the world addressing problem that there was no down period for service ... where downtime/outages could be tolerated for things like preventive maintenance. They would migrate virtual machines as part of dynamically taking complexes offline (out of the cluster)for service. misc. past posts mentioning the virtual machine commercial timesharing services dating back to 60s: http://www.garlic.com/~lynn/subtopic.html#timeshare The largest such of the clustering (single system image) operations in the late 70s (not limited to vm systems, but any mainframe complex, anywhere) was the US VM-based internal (worldwide) salesmarketing support HONE system that. The US HONE centers had been consolidated in bldg. (they no longer occupy the bldg, but it is located next door to the new facebook bldg ). This US datacenter was the largest (although other HONE clones had started to spring up several places around the world) with load-balancing and fall-over recovery. Then because of earthquake concern, in the early 80s, the cal. center was first replicated in Dallas and then a 3rd in Boulder (with load-balancing and fall-over across the redundant centers). a few recent posts in Greater IBM discussing HONE: http://www.garlic.com/~lynn/2010d.html#27 HONE VMSHARE http://www.garlic.com/~lynn/2010e.html#24 Unbundling HONE http://www.garlic.com/~lynn/2010e.html#25 HONE Compute Intensive http://www.garlic.com/~lynn/2010e.html#29 HONE VMSHARE misc. ohter posts mentioning HONE http://www.garlic.com/~lynn/subtopic.html#hone The product to customers saw big impact when POK got the development group shutdown and all the people moved to POK to support MVS/XA development. initially the product was also killed, Endicott managed to save the product mission... but had to reconstitute a group from scratch. This possibly contributed to the VM/SP quality mentioned in Melinda's history ... recent reference: http://www.garlic.com/~lynn/2010e.html#31 What was old is new again (water chilled) http://www.garlic.com/~lynn/2010e.html#36 What was old is new again (water chilled) The 4331/4341 saw big explosion in distributed machines connected via network ... so the (their new) focus wasn't on the highend and/or clustering in single location. There was a research clustering project, eight 4341s with 3088 ... that eventually offered as product ... but that ran into a couple problems 1) there was already pressure from high-end (mvs, 3033, 3081s, etc) where customers found that multiple vm/4341s were much more cost effective than the big iron ... so anything that enhanced this, was met with opposition. 2) the internal product had things like cluster-wide operations taking very small subsecond elapsed time. however, for product ship they were forced to move to SNA ... and all of a sudden simple cluster-wide coordination operations were taking nearly a minute elapsed time. This is similar to the on-going SNA battles that my wife faced when she had been con'ed into going to POK to be in charge of (high-end) mainframe loosely-coupled architecture. The battles with SNA (ephemeral temporary truces where she could use anything she wanted with datacenter walls but SNA had to be used by anything crossing the walls of the datacenters) and very little uptake at the time (except for IMS hot-standby until sysplex) met that she didn't stay long ... misc. past posts mentioning her peer-coupled shared data architecture http://www.garlic.com/~lynn/submain.html#shareddata -- 42yrs virtualization experience (since Jan68), online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On Sat, Mar 6, 2010 at 8:46 AM, Eric Bielefeld eric-ibmm...@wi.rr.comwrote: I'm curious. The last release of VM I really worked with was 5.1 - no XP or later stuff. Has it changed much, or are most of the concepts still the same? Hm, VM/XP...now that's a scary thought! (Great typo!) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Oooops. Eric Bielefeld Sr. Systems Programmer IBM Global Services Division Dubuque, Iowa 414-477-7259 - Original Message - From: zMan zedgarhoo...@gmail.com Newsgroups: bit.listserv.ibm-main To: IBM-MAIN@bama.ua.edu Sent: Saturday, March 06, 2010 10:22 AM Subject: Re: LPARs: More or Less? On Sat, Mar 6, 2010 at 8:46 AM, Eric Bielefeld eric-ibmm...@wi.rr.comwrote: I'm curious. The last release of VM I really worked with was 5.1 - no XP or later stuff. Has it changed much, or are most of the concepts still the same? Hm, VM/XP...now that's a scary thought! (Great typo!) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Hi Rich, Thanks for the information. A couple of years before PH Minings z/OS datacenter shut down, I kind of suspected that the end was coming. I took 3 courses on Linux Administration from one of the technical colleges around Milwaukee. I had the hopes that having worked with VM, and learning about Linux might help me in getting a job. I never found any jobs related to Linux or VM, but it was very interesting. I loaded Linux on my laptop, and used it under dual boot. That was very useful when I was working on the classes, since when I was reading about a command, I could run it and try various options. Alas, when my laptop was getting near the end of the 3 year warranty, I needed to get a couple of things fixed. Naturally, they reloaded the original XP operatings system and wiped out my Linux partition. Think about what would happen if z/OS people worked the same as Windows people! Eric Bielefeld Sr. Systems Programmer IBM Global Services Division Dubuque, Iowa 414-477-7259 - Original Message - From: Rich Smrcina r...@velocitysoftware.com VM has changed considerably since HPO 5.1. Long gone are the days of assembling modules to apply service and to add devices (thank god). To the sysprog servicing VM is pretty much two commands (after the service envelope is uploaded). And of course all modern devices can be sensed. Most of the new support now centers around capacity (very large virtual machines) and virtual networking (virtual switch). There is a statement of direction for clustering (not sysplex) and guest migration (moving live machines between VM systems). All of this with the intent of supporting Linux. The motherhood and apple pie concepts of VM haven't changed much since HPO. The line oriented commands, XEDIT, etc Rich Smrcina Phone: 414-491-6001 http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2010 - Apr 9-13, 2010 Covington, KY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
I've worked with VM since the 70s. SP1 to be more precise. Well actually there was this little thing called CP67, but that's a much longer story. VM has certainly grown over time while keeping its good strong basics. The current release of zVM includes more cooperative support for Linux guests and for z/OS guests to use specialty processors. As a software vendor, we support 100s of guests. It is (and remains IMHO) industrial strength for this type of need. znor...@ca.com -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of zMan Sent: Saturday, March 06, 2010 SYSN 08:22 AM To: IBM-MAIN@bama.ua.edu Subject: Re: LPARs: More or Less? On Sat, Mar 6, 2010 at 8:46 AM, Eric Bielefeld eric-ibmm...@wi.rr.comwrote: I'm curious. The last release of VM I really worked with was 5.1 - no XP or later stuff. Has it changed much, or are most of the concepts still the same? Hm, VM/XP...now that's a scary thought! (Great typo!) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On Sat, Mar 6, 2010 at 1:41 PM, Norman Hollander on DesertWiz norman.hollan...@desertwiz.biz wrote: I've worked with VM since the 70s. SP1 to be more precise. Well actually there was this little thing called CP67, but that's a much longer story. VM has certainly grown over time while keeping its good strong basics. The current release of zVM includes more cooperative support for Linux guests and for z/OS guests to use specialty processors. As a software vendor, we support 100s of guests. It is (and remains IMHO) industrial strength for this type of need. Do you mean VM/370 Release 1? Because VM/SP Release 1 wasn't announced until February 1980. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
In a message dated 3/6/2010 10:23:27 A.M. Central Standard Time, zedgarhoo...@gmail.com writes: Hm, VM/XP...now that's a scary thought! (Great typo!) 'bout the maddest I ever saw anybody in a suit was the MVS/XA ESP rollout and 'Oh and VM support wouldn't be available for another six months'. The VP was a chrome dome and you could see the pressure build from the neck up. Wrath of Kahn... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
You'd be correct. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of zMan Sent: Saturday, March 06, 2010 SYSN 10:47 AM To: IBM-MAIN@bama.ua.edu Subject: Re: LPARs: More or Less? On Sat, Mar 6, 2010 at 1:41 PM, Norman Hollander on DesertWiz norman.hollan...@desertwiz.biz wrote: I've worked with VM since the 70s. SP1 to be more precise. Well actually there was this little thing called CP67, but that's a much longer story. VM has certainly grown over time while keeping its good strong basics. The current release of zVM includes more cooperative support for Linux guests and for z/OS guests to use specialty processors. As a software vendor, we support 100s of guests. It is (and remains IMHO) industrial strength for this type of need. Do you mean VM/370 Release 1? Because VM/SP Release 1 wasn't announced until February 1980. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. Dave g8...@yahoo.com writes: Well VM or CP is very different. As the XA/ESA/z machine can't be virtualized easily in software, I assume because of the need to make AMODE switchs efficient, CP now relies on the SIE instruction to provide virtual machines. I gather this uses the same hardware that LPARs use. I guess you might consider this a superset of the VM Assists that were available on S/370... XA wasn't as easily virtualized as 360 370 was ... and therefor the SIE instruction. SIE predates PR/SM and LPARs ... in that sense PR/SM and LPARs were leveraging the pre-existing infrastructure for microcode assists and SIE (and for some time, some of the assist microcode was mutually exclusive, either for VM use or LPAR use ... but not both). In the 360/370 scenario ... LPSW and interrupts loaded new PSW ... which simultaneously switched address space and privilege/problem mode in single operation (in MVS, a copy of the kernel appears in every address space ... where in cp/vm, the kernel and the guest address spaces are totally distinct). SIE was able to change address spaces and privilege/problem mode in single operation, as well as set a flag for privilege instructions ... basically assist mode that indicates privilege instruction is executed according to virtual machine rules (as opposed to real machine rules, basically each assisted privilege instruction has modified microcode). To simulataneously use the assists for LPARs and virtual machines ... effectively needed each privilege instruction microcode to be further modified to recognize 1) real machine, no LPAR, no virtual machine, 2) LPAR, no virtual machine, 3) virtual machine, no LPAR, 4) both LPAR and virtual machine. From a microcode standpoint, LPAR+VM is similar to virtualizing SIE (i.e. running a guest VM system under a VM virtual machine). SIE had additional performance issues on 3081 ... starting out just purely being internal tool supporting mvx/xa development ... originally never intended for shipping to customers (or production use). ... recent references to 3081 SIE microcode was paged (i.e. 3081 service processing paging SIE microcode from 3310 FBA ... representing something of performance issue): http://www.garlic.com/~lynn/2010e.html#34 Need tool to zap core http://www.garlic.com/~lynn/2010e.html#44 Need tool to zap core http://www.garlic.com/~lynn/2010e.html#46 Impact of solid-state drives the other is the emulated implementations ... like Hercules ... implemented on Intel platform; this could be considered analogous to the entry mid-range mainframe implementations that had been done in vertical microcode. There was a separate performance issue going from virtual MVT guests to virtual SVS/MVS guests ... since VM started out simulating the TLB (hardware look aside buffer implementing virtual memory) with shadow page tables. The management of the entries in the shadow page tables with software was enormously slower than the hardware overhead involved in managing TLB entries. There could also be pathelogical page replacement algorithm behavior ... with MVS approximating a LRU page replacement and VM also approximating a LRU page replacement ... VM might be selecting the MVS guest page for removal from real storage ... moments before the MVS guest desides that it is the ideal next page to use (VM deciding that since it hasn't been used, it can be removed from real storage and MVS deciding that since it hasn't been used, it can be reassigned for some other use). -- 42yrs virtualization experience (since Jan68), online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
In 1413410174-1267806280-cardhu_decombobulator_blackberry.rim.net-10510679...@bda026.bisx.prod.on.blackberry, on 03/05/2010 at 04:24 PM, Ted MacNEIL eamacn...@yahoo.ca said: Outside of IBM, I've only met two people with VM and MVS skills. This is in the Greater Toronto Area, over the last 30 years. To me, that's rare. Very well; I retract my original response. Instead, I'll state that it's not at all rare outside of the Greater Toronto Metropolitan Area. I'm not, however, ruling out the possibility that there are lots of people in toronto with both skill sets that you simply haven't met. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
George: That's interesting to me that you would suggest IBM will give z/VM for free to hospitals. I am presently consulting at a hospital that is moving away from z/OS and moving their primary applications to the mid-range. I would like to get the to look at using the mainframe for Linux, under z/VM. Could you provide me with a link or reference to the IBM program or policy that is proposing this offering? Mike Myers Mentor Services Corporation (919) 341-5210 On 3/5/2010 12:23 PM, George Henke wrote: It wasn't until zLinux popped up that I started working with VM again, which I think is getting more and more common, so the dual skill set ismaking a come back. You're absolutely right, Mark. I know a very large financial company who is doing just that after the project was languishing for 6 years. Also, it should be noted, that IBM offers z/VM virtually for free to hospitals and universities as long as they use it for research. So you will find z/VM and z/OS living happily together at such institutions which is where I installed z/VM 5.4 last November. On Fri, Mar 5, 2010 at 12:13 PM, Mark Zeldenmzel...@flash.net wrote: On Fri, 5 Mar 2010 16:24:51 +, Ted MacNEILeamacn...@yahoo.ca wrote: No, I wouldn't call it popular, but I wouldn't call it rare either. I have worked on VM off and on throughout my career. Outside of IBM, I've only met two people with VM and MVS skills. This is in the Greater Toronto Area, over the last 30 years. To me, that's rare. That is your experience, which is what you are writing about. I will say it is much more rare these days than it was 20 years ago. At least in the Chicago area. There used to be a lot of shops running VM along with MVS (and hence many sysprogs with experience in both) but many of them got rid of VM. The last full time VM I supported was VM/XA but I also worked with VM/ESA and VM/HPO not long after that but there was a full time VM sysprog that really supported those environments when I worked on them. It wasn't until zLinux popped up that I started working with VM again, which I think is getting more and more common, so the dual skill set is making a come back. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
George Henke pisze: I think I may have finally come upon a valid justification for a separate UAT, QA LPAR; maybe the only justification. You can only have one instance of Security, RACF, ACF2, TSS, in an LPAR, z/OS Domain, at any one time. You SHOULD have only one kind of Security Server in all shop, especially DEV-TEST_UAT-whatever-PROD chain. Since, for QA testing, the need is to mirror PROD Security so that the security rules for a change being made are tested *before* moving the change to PROD, then there would need to be a separate LPAR to hold a separate Security DB that mirrored the PROD DB. It is good idea to have set of security rules for application independent of system. In other words it should be possible to have multiple instances of the application, each with *their own* security rules. Since the DEV LPAR already has a DEV Security DB and there can be only one instance of a Security DB per LPAR, this would preclude the mirroring of the PROD Security DB in a DEV LPAR, and is sufficient reason for creating a separate LPAR for QA, UAT, testing. See above. IMNSHO it is *bad design* to have single security for all instances. [...] However, it still begs the question, why have LPARs at all, because separate Security DBs *can* be configured in separate Virtual Machines running separate instances of z/OS under z/VM without LPARs at all. MONEY! z/VM is NOT freeware and requires people/skills for administration. PR/SM is free, LPAR configuration is easier than z/VM installation, setup, etc. and cannot be avoided (you must have LPARs). -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237 NIP: 526-021-50-88 Wedug stanu na dzie 01.01.2009 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 118.763.528 zotych. W zwizku z realizacj warunkowego podwyszenia kapitau zakadowego, na podstawie uchway XXI WZ z dnia 16 marca 2008r., oraz uchway XVI NWZ z dnia 27 padziernika 2008r., moe ulec podwyszeniu do kwoty 123.763.528 z. Akcje w podwyszonym kapitale zakadowym BRE Banku SA bd w caoci opacone. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
In 999072802-1267753158-cardhu_decombobulator_blackberry.rim.net-10413382...@bda026.bisx.prod.on.blackberry, on 03/05/2010 at 01:39 AM, Ted MacNEIL eamacn...@yahoo.ca said: VM MVS skills are rare to find in the same individual(s). Not all that rare. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
-Original Message- From: IBM Mainframe Discussion List On Behalf Of George Henke I think I may have finally come upon a valid justification for a separate UAT, QA LPAR; maybe the only justification. You can only have one instance of Security, RACF, ACF2, TSS, in an LPAR, z/OS Domain, at any one time. OK so far Since, for QA testing, the need is to mirror PROD Security so that the security rules for a change being made are tested *before* moving the change to PROD, then there would need to be a separate LPAR to hold a separate Security DB that mirrored the PROD DB. We use installation-defined classes for much of that separation, which works well here because the vast majority of resources for which we might need to test new security rules are amenable to separate cloned classes (mostly CICS and FACILITY-like stuff). Since the DEV LPAR already has a DEV Security DB and there can be only one instance of a Security DB per LPAR, this would preclude the mirroring of the PROD Security DB in a DEV LPAR, and is sufficient reason for creating a separate LPAR for QA, UAT, testing. Actually, we share a RACF database between PROD and DEV/QA. Only the sandbox has a separate RACF database. Of all the justifications, presented thus far, for creating a separate LPAR for QA, UAT testing, this appears to be the only one that cannot be refuted. If any exception to the rule counts as refutation, this is refuted. However, it still begs the question, why have LPARs at all, because separate Security DBs *can* be configured in separate Virtual Machines running separate instances of z/OS under z/VM without LPARs at all. OTOH, if all you run is a relatively stable set of z/OS images, why use z/VM when PR/SM is free (indeed, you can't get a current CPC without it)? I'll admit that I've not worked with any flavor of VM in over a decade, but I don't recall any flavor of MVS IPLing any faster under VM than in an LPAR. -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
No, I wouldn't call it popular, but I wouldn't call it rare either. I have worked on VM off and on throughout my career. Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net 3/5/2010 6:05 AM In 999072802-1267753158-cardhu_decombobulator_blackberry.rim.net-10413382...@bda026.bisx.prod.on.blackberry, on 03/05/2010 at 01:39 AM, Ted MacNEIL eamacn...@yahoo.ca said: VM MVS skills are rare to find in the same individual(s). Not all that rare. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Thank you all for your constructive comments and critiques. But from this little brainstorming exercise, I believe if I have learned anything at all, I have learned that PR/SM is anything but free. Would IBM really give away anything for free? Here's nothing, grab it well (Old Hungarian proverb) The easiest path, the path of least resistance, is not always optimum. There is a very hidden, subtle, but quite exorbitant price paid for PR/SM: - Memory for each instance of z/OS replicated, - Performance: wasted CPU cycles especially for handshaking between LPARs doing shared I/O, - Software licensing fees - Inflexibility of fitting workloads into fixed partitions, - complexity: After splitting everything up we bring it all back together again with Parallel Sysplex, CDSes, CFRM policies: List, Cache, and Lock structures, all kinds of plexes: JESPLEX, VTAMPLEX, IMSPLEX, VSAM RLS, CICSPLEX, SHARED DB2, all designed to circumvent the artificial barriers we never needed to erect in the first place. despite: - all efforts of IBM to encourage this with sub-capacity pricing - the diminishing need to carve up memory now that paging, Expanded Storage, are history with 64 bit memory. True, there is a place for PR/SM for things like CFCC, AIX, LINUX. But just needlessly replicating z/OS because it is free and easy to do is not the answer. One of the oldest marketing devices is: - to first lower the hemline, then raise it; - first bring out double knit men's suits, then banish them, - first tell everyone to go distributive, then force them to centralize, - and above all: - software sells hardware, so encourage the inefficient use, needless replication, of software so we can sell more hardware. On Fri, Mar 5, 2010 at 8:00 AM, Chase, John jch...@ussco.com wrote: -Original Message- From: IBM Mainframe Discussion List On Behalf Of George Henke I think I may have finally come upon a valid justification for a separate UAT, QA LPAR; maybe the only justification. You can only have one instance of Security, RACF, ACF2, TSS, in an LPAR, z/OS Domain, at any one time. OK so far Since, for QA testing, the need is to mirror PROD Security so that the security rules for a change being made are tested *before* moving the change to PROD, then there would need to be a separate LPAR to hold a separate Security DB that mirrored the PROD DB. We use installation-defined classes for much of that separation, which works well here because the vast majority of resources for which we might need to test new security rules are amenable to separate cloned classes (mostly CICS and FACILITY-like stuff). Since the DEV LPAR already has a DEV Security DB and there can be only one instance of a Security DB per LPAR, this would preclude the mirroring of the PROD Security DB in a DEV LPAR, and is sufficient reason for creating a separate LPAR for QA, UAT, testing. Actually, we share a RACF database between PROD and DEV/QA. Only the sandbox has a separate RACF database. Of all the justifications, presented thus far, for creating a separate LPAR for QA, UAT testing, this appears to be the only one that cannot be refuted. If any exception to the rule counts as refutation, this is refuted. However, it still begs the question, why have LPARs at all, because separate Security DBs *can* be configured in separate Virtual Machines running separate instances of z/OS under z/VM without LPARs at all. OTOH, if all you run is a relatively stable set of z/OS images, why use z/VM when PR/SM is free (indeed, you can't get a current CPC without it)? I'll admit that I've not worked with any flavor of VM in over a decade, but I don't recall any flavor of MVS IPLing any faster under VM than in an LPAR. -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Wow, I just don't know where to start. The comments about PR/SM being free were made in the context of comparing it to using VM, and in that sense it is free since using VM not only has a license cost, but would further increase all the other costs you outline. You seem to be implying that companies use PR/SM on a whim to multiply their z/OS images for no good reason, which I think is preposterous. You say that all the points made have been refuted, yet you quietly fail to even acknowledge many very strong arguments. It has not been terribly clear from the start what your position really is. Are you arguing that there is no point in having more that one z/OS image on any CEC, or are you arguing that PR/SM is a waste, and everyone should be using VM? You seem to have argued both points at various times. George Henke gahe...@gmail.com 3/5/2010 9:38 AM Thank you all for your constructive comments and critiques. But from this little brainstorming exercise, I believe if I have learned anything at all, I have learned that PR/SM is anything but free. Would IBM really give away anything for free? Here's nothing, grab it well (Old Hungarian proverb) The easiest path, the path of least resistance, is not always optimum. There is a very hidden, subtle, but quite exorbitant price paid for PR/SM: - Memory for each instance of z/OS replicated, - Performance: wasted CPU cycles especially for handshaking between LPARs doing shared I/O, - Software licensing fees - Inflexibility of fitting workloads into fixed partitions, - complexity: After splitting everything up we bring it all back together again with Parallel Sysplex, CDSes, CFRM policies: List, Cache, and Lock structures, all kinds of plexes: JESPLEX, VTAMPLEX, IMSPLEX, VSAM RLS, CICSPLEX, SHARED DB2, all designed to circumvent the artificial barriers we never needed to erect in the first place. despite: - all efforts of IBM to encourage this with sub-capacity pricing - the diminishing need to carve up memory now that paging, Expanded Storage, are history with 64 bit memory. True, there is a place for PR/SM for things like CFCC, AIX, LINUX. But just needlessly replicating z/OS because it is free and easy to do is not the answer. One of the oldest marketing devices is: - to first lower the hemline, then raise it; - first bring out double knit men's suits, then banish them, - first tell everyone to go distributive, then force them to centralize, - and above all: - software sells hardware, so encourage the inefficient use, needless replication, of software so we can sell more hardware. On Fri, Mar 5, 2010 at 8:00 AM, Chase, John jch...@ussco.com wrote: -Original Message- From: IBM Mainframe Discussion List On Behalf Of George Henke I think I may have finally come upon a valid justification for a separate UAT, QA LPAR; maybe the only justification. You can only have one instance of Security, RACF, ACF2, TSS, in an LPAR, z/OS Domain, at any one time. OK so far Since, for QA testing, the need is to mirror PROD Security so that the security rules for a change being made are tested *before* moving the change to PROD, then there would need to be a separate LPAR to hold a separate Security DB that mirrored the PROD DB. We use installation-defined classes for much of that separation, which works well here because the vast majority of resources for which we might need to test new security rules are amenable to separate cloned classes (mostly CICS and FACILITY-like stuff). Since the DEV LPAR already has a DEV Security DB and there can be only one instance of a Security DB per LPAR, this would preclude the mirroring of the PROD Security DB in a DEV LPAR, and is sufficient reason for creating a separate LPAR for QA, UAT, testing. Actually, we share a RACF database between PROD and DEV/QA. Only the sandbox has a separate RACF database. Of all the justifications, presented thus far, for creating a separate LPAR for QA, UAT testing, this appears to be the only one that cannot be refuted. If any exception to the rule counts as refutation, this is refuted. However, it still begs the question, why have LPARs at all, because separate Security DBs *can* be configured in separate Virtual Machines running separate instances of z/OS under z/VM without LPARs at all. OTOH, if all you run is a relatively stable set of z/OS images, why use z/VM when PR/SM is free (indeed, you can't get a current CPC without it)? I'll admit that I've not worked with any flavor of VM in over a decade, but I don't recall any flavor of MVS IPLing any faster under VM than in an LPAR. -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives
Re: LPARs: More or Less?
At the end of the day, this discussion comes down to business requirements. Many institutions, due to audit, regulatory, or industry standards need to separate SANDBOX/DEV/TEST/QA/PROD. This can be done at the administrative level (1 big LPAR with all information(os testing excluded)), or the image level(separate LPARS for each), z/VM guests, or anything in between. The trick in the single image environment is proving that the non-production user CANNOT access production data, which will be a concern for even the most incompetent of auditors. Yes this can be accomplished, but how many auditors will understand the nuances of RACF/ACF2/TS enough to even test the premise. Not to mention the administrative overhead required to establish, document, and maintain the separation of the environments within a single image. A separate LPAR(or guest) can be easily defended (with backup doc from IBM and others) by saying This LPAR cannot access that LPAR's data unless explicitly allowed. Most auditors can understand and test that premise, even if they are not security experts. In other words, whatever works best for your business is the method you should use. Just my 0.02 USD worth, -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
-Original Message- From: IBM Mainframe Discussion List On Behalf Of George Henke Thank you all for your constructive comments and critiques. But from this little brainstorming exercise, I believe if I have learned anything at all, I have learned that PR/SM is anything but free. Would IBM really give away anything for free? The price of PR/SM is built-in to the price of the hardware, so it appears free. You get it regardless whether you ever use it; very much like the free air bags and seat belts you get in a car nowadays. Here's nothing, grab it well (Old Hungarian proverb) The easiest path, the path of least resistance, is not always optimum. Which tacitly acknowledges that on occasion it is. There is a very hidden, subtle, but quite exorbitant price paid for PR/SM: - Memory for each instance of z/OS replicated, - Performance: wasted CPU cycles especially for handshaking between LPARs doing shared I/O, - Software licensing fees - Inflexibility of fitting workloads into fixed partitions, - complexity: After splitting everything up we bring it all back together again with Parallel Sysplex, CDSes, CFRM policies: List, Cache, and Lock structures, all kinds of plexes: JESPLEX, VTAMPLEX, IMSPLEX, VSAM RLS, CICSPLEX, SHARED DB2, all designed to circumvent the artificial barriers we never needed to erect in the first place. It was my understanding that all those various plexes were designed to reduce or eliminate single points of failure, thus providing the capability for near-continuous operation. despite: - all efforts of IBM to encourage this with sub-capacity pricing - the diminishing need to carve up memory now that paging, Expanded Storage, are history with 64 bit memory. Paging is alive and well despite 64-bit storage. True, there is a place for PR/SM for things like CFCC, AIX, LINUX. But just needlessly replicating z/OS because it is free and easy to do is not the answer. Some might argue that z/VM makes needlessly replicating z/OS even easier. I think the key word here is needlessly: How many installations needlessly replicate z/OS? One of the oldest marketing devices is: - to first lower the hemline, then raise it; - first bring out double knit men's suits, then banish them, - first tell everyone to go distributive, then force them to centralize, - and above all: - software sells hardware, so encourage the inefficient use, needless replication, of software so we can sell more hardware. Bigger, faster cars that consumed lots of fuel were once the rage. Then the fuel providers decided they could raise their prices, so they raised them until smaller, more fuel-efficient cars became the new rage. But drivers sorely missed bigger and faster, so they demanded they be reinstated. Green side out, now brown side out, now green side out again. That's the way things work. Enjoy the ride, for in the end we shall all be dead. -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
You seem to be implying that companies use PR/SM on a whim to multiply their z/OS images for no good reason, which I think is preposterous. You're right it is preposterous. The only thing the PR/SM LPAR paradigm lacks is a nice Escher painting to hang over it. On Fri, Mar 5, 2010 at 11:04 AM, George Henke gahe...@gmail.com wrote: Auditors don't like anything they can't stub their toe on. I have the scares to prove it. On Fri, Mar 5, 2010 at 10:52 AM, Staller, Allan allan.stal...@kbm1.comwrote: At the end of the day, this discussion comes down to business requirements. Many institutions, due to audit, regulatory, or industry standards need to separate SANDBOX/DEV/TEST/QA/PROD. This can be done at the administrative level (1 big LPAR with all information(os testing excluded)), or the image level(separate LPARS for each), z/VM guests, or anything in between. The trick in the single image environment is proving that the non-production user CANNOT access production data, which will be a concern for even the most incompetent of auditors. Yes this can be accomplished, but how many auditors will understand the nuances of RACF/ACF2/TS enough to even test the premise. Not to mention the administrative overhead required to establish, document, and maintain the separation of the environments within a single image. A separate LPAR(or guest) can be easily defended (with backup doc from IBM and others) by saying This LPAR cannot access that LPAR's data unless explicitly allowed. Most auditors can understand and test that premise, even if they are not security experts. In other words, whatever works best for your business is the method you should use. Just my 0.02 USD worth, -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Many disagreements (interspersed): There is a very hidden, subtle, but quite exorbitant price paid for PR/SM: Define exhorbitant. - Memory for each instance of z/OS replicated, Memory is relatively cheap compared to the total cost of the processor. - Performance: wasted CPU cycles especially for handshaking between LPARs doing shared I/O, I've been involved in MDF PR/SM since the mid-1980's. Back then, MDF was expensive -- 5% of the processor per domain. PR/SM -- 3090-base -- 7% -- 3090-E -- 5-6% -- 3090-S -- 5ish% -- 3090-J -- 4-5% -- ES/9000-- 4-5% -- 9672-- 3-4% -- z/Box -- 2-3% These are from memory following IBM guidelines on the number of logical vs physical ratios. I was responsible for the measurements, and they were done by me, for many different environments that I managed. I only suffered twice from I/O elongation, and both were on the older (non-CMOS) technology. TPI EMIF addressed a lot of the I/O issues. DCM (HIPER)PAV addressed a lot more. With sub-5ms response, it's almost impossible to discern any effects due to PR/SM. - Software licensing fees - Inflexibility of fitting workloads into fixed partitions, Again, define inflexibility. With variable weights, CPUs, and other dynamism in the picture, surely there is great flexibility. Would you want to go back to the old monoliths with the (implied) wasted capacity. Also, by isolating specific workloads to smaller partitions, I have helped many companies save licensing costs. - complexity: After splitting everything up we bring it all back together again with Parallel Sysplex, CDSes, CFRM policies: List, Cache, and Lock structures, all kinds of plexes: JESPLEX, VTAMPLEX, IMSPLEX, VSAMRLS, CICSPLEX, SHARED DB2, all designed to circumvent the artificial barriers we never needed to erect in the first place. That has nothing to do with PR/SM. SYSPLEX complexity is for redundancy in case of failure of hardware, systems, or sub-systems. The first SYSPLEX, I was involved in, was four monolithic (ie: non-partitioned) processors. We went to PR/SM, on one new box, to replace two boxes, about a year later. The reasons for PR/SM, in that case were: 1. Less power. 2. Less cooling. 3. Flexibility. The two images peaked at different times, so we could get away with less capacity than that required by two footprints. 4. Of course, software costs. One less MVS licence. despite: - all efforts of IBM to encourage this with sub-capacity pricing Sub-Capacity Licences DO save money. - the diminishing need to carve up memory now that paging, Expanded Storage, are history with 64 bit memory. One agreement. True, there is a place for PR/SM for things like CFCC, AIX, LINUX. But just needlessly replicating z/OS because it is free and easy to do is not the answer. Why not? There is more to it than your simple dismissal. There are isolation issues. And, even in the 21st century, virtual storage issues, still. That is to name just two. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
No, I'm saying that it's preposterous for you to say such a thing, because I do not believe it is prevalent. I have never seen such a situation in any shop where I have worked, nor have I heard any reliable source explain that such a situation exists elsewhere. I recently was involved in situation where management was desiring to do such a thing, through their own ignorance of the technology, but I was able to defeat it. George Henke gahe...@gmail.com 3/5/2010 11:50 AM You seem to be implying that companies use PR/SM on a whim to multiply their z/OS images for no good reason, which I think is preposterous. You're right it is preposterous. The only thing the PR/SM LPAR paradigm lacks is a nice Escher painting to hang over it. On Fri, Mar 5, 2010 at 11:04 AM, George Henke gahe...@gmail.com wrote: Auditors don't like anything they can't stub their toe on. I have the scares to prove it. On Fri, Mar 5, 2010 at 10:52 AM, Staller, Allan allan.stal...@kbm1.comwrote: At the end of the day, this discussion comes down to business requirements. Many institutions, due to audit, regulatory, or industry standards need to separate SANDBOX/DEV/TEST/QA/PROD. This can be done at the administrative level (1 big LPAR with all information(os testing excluded)), or the image level(separate LPARS for each), z/VM guests, or anything in between. The trick in the single image environment is proving that the non-production user CANNOT access production data, which will be a concern for even the most incompetent of auditors. Yes this can be accomplished, but how many auditors will understand the nuances of RACF/ACF2/TS enough to even test the premise. Not to mention the administrative overhead required to establish, document, and maintain the separation of the environments within a single image. A separate LPAR(or guest) can be easily defended (with backup doc from IBM and others) by saying This LPAR cannot access that LPAR's data unless explicitly allowed. Most auditors can understand and test that premise, even if they are not security experts. In other words, whatever works best for your business is the method you should use. Just my 0.02 USD worth, -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On Fri, 5 Mar 2010 16:24:51 +, Ted MacNEIL eamacn...@yahoo.ca wrote: No, I wouldn't call it popular, but I wouldn't call it rare either. I have worked on VM off and on throughout my career. Outside of IBM, I've only met two people with VM and MVS skills. This is in the Greater Toronto Area, over the last 30 years. To me, that's rare. That is your experience, which is what you are writing about. I will say it is much more rare these days than it was 20 years ago. At least in the Chicago area. There used to be a lot of shops running VM along with MVS (and hence many sysprogs with experience in both) but many of them got rid of VM. The last full time VM I supported was VM/XA but I also worked with VM/ESA and VM/HPO not long after that but there was a full time VM sysprog that really supported those environments when I worked on them. It wasn't until zLinux popped up that I started working with VM again, which I think is getting more and more common, so the dual skill set is making a come back. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
No, I'm saying that it's preposterous for you to say such a thing, because I do not believe it is prevalent. . . . I recently was involved in situation where management was desiring to do such a thing, through their own ignorance of the technology, but I was able to defeat it. IBM owes you money. On Fri, Mar 5, 2010 at 11:59 AM, Scott Rowe scott.r...@joann.com wrote: No, I'm saying that it's preposterous for you to say such a thing, because I do not believe it is prevalent. I have never seen such a situation in any shop where I have worked, nor have I heard any reliable source explain that such a situation exists elsewhere. I recently was involved in situation where management was desiring to do such a thing, through their own ignorance of the technology, but I was able to defeat it. George Henke gahe...@gmail.com 3/5/2010 11:50 AM You seem to be implying that companies use PR/SM on a whim to multiply their z/OS images for no good reason, which I think is preposterous. You're right it is preposterous. The only thing the PR/SM LPAR paradigm lacks is a nice Escher painting to hang over it. On Fri, Mar 5, 2010 at 11:04 AM, George Henke gahe...@gmail.com wrote: Auditors don't like anything they can't stub their toe on. I have the scares to prove it. On Fri, Mar 5, 2010 at 10:52 AM, Staller, Allan allan.stal...@kbm1.comwrote: At the end of the day, this discussion comes down to business requirements. Many institutions, due to audit, regulatory, or industry standards need to separate SANDBOX/DEV/TEST/QA/PROD. This can be done at the administrative level (1 big LPAR with all information(os testing excluded)), or the image level(separate LPARS for each), z/VM guests, or anything in between. The trick in the single image environment is proving that the non-production user CANNOT access production data, which will be a concern for even the most incompetent of auditors. Yes this can be accomplished, but how many auditors will understand the nuances of RACF/ACF2/TS enough to even test the premise. Not to mention the administrative overhead required to establish, document, and maintain the separation of the environments within a single image. A separate LPAR(or guest) can be easily defended (with backup doc from IBM and others) by saying This LPAR cannot access that LPAR's data unless explicitly allowed. Most auditors can understand and test that premise, even if they are not security experts. In other words, whatever works best for your business is the method you should use. Just my 0.02 USD worth, -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
It wasn't until zLinux popped up that I started working with VM again, which I think is getting more and more common, so the dual skill set is making a come back. You're absolutely right, Mark. I know a very large financial company who is doing just that after the project was languishing for 6 years. Also, it should be noted, that IBM offers z/VM virtually for free to hospitals and universities as long as they use it for research. So you will find z/VM and z/OS living happily together at such institutions which is where I installed z/VM 5.4 last November. On Fri, Mar 5, 2010 at 12:13 PM, Mark Zelden mzel...@flash.net wrote: On Fri, 5 Mar 2010 16:24:51 +, Ted MacNEIL eamacn...@yahoo.ca wrote: No, I wouldn't call it popular, but I wouldn't call it rare either. I have worked on VM off and on throughout my career. Outside of IBM, I've only met two people with VM and MVS skills. This is in the Greater Toronto Area, over the last 30 years. To me, that's rare. That is your experience, which is what you are writing about. I will say it is much more rare these days than it was 20 years ago. At least in the Chicago area. There used to be a lot of shops running VM along with MVS (and hence many sysprogs with experience in both) but many of them got rid of VM. The last full time VM I supported was VM/XA but I also worked with VM/ESA and VM/HPO not long after that but there was a full time VM sysprog that really supported those environments when I worked on them. It wasn't until zLinux popped up that I started working with VM again, which I think is getting more and more common, so the dual skill set is making a come back. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
That's your reply? IBM owes me money? Why? Because I did my job? Now you will probably go on to say that nobody has refuted your position, right? Are you really interested in having an intelligent discussion here? You seem to just be posting long diatribes and ignoring or dismissing all the well thought out responses you receive. I'm still kind of curious what exactly you mean by: - Performance: wasted CPU cycles especially for handshaking between LPARs doing shared I/O I have thoughts on what you mean by these kinds of things, but I am reserving judgement. George Henke gahe...@gmail.com 3/5/2010 12:15 PM No, I'm saying that it's preposterous for you to say such a thing, because I do not believe it is prevalent. . . . I recently was involved in situation where management was desiring to do such a thing, through their own ignorance of the technology, but I was able to defeat it. IBM owes you money. CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
I'm still kind of curious what exactly you mean by: - Performance: wasted CPU cycles especially for handshaking between LPARs doing shared I/O So am I. I haven't seen these issues since the early days of MDF and PR/SM in the 1980's. I have thoughts on what you mean by these kinds of things, but I am reserving judgement. I'm not. This sounds like a diatribe against something that has matured in the last 25 years. Rather than say it's bad because I say it's bad, present some evidence. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less? (OT, somewhat)
Ah, the good old GTA; come visit Edmonton, Ted. There are a number of ambidextrous sysprogs in our area. (Not to put T.O. down - I lived there during the 60's 70's and loved it.) -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ted MacNEIL Sent: Friday, March 05, 2010 9:25 AM To: IBM-MAIN@bama.ua.edu Subject: Re: LPARs: More or Less? No, I wouldn't call it popular, but I wouldn't call it rare either. I have worked on VM off and on throughout my career. Outside of IBM, I've only met two people with VM and MVS skills. This is in the Greater Toronto Area, over the last 30 years. To me, that's rare. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html The information transmitted is intended only for the addressee and may contain confidential, proprietary and/or privileged material. Any unauthorized review, distribution or other use of or the taking of any action in reliance upon this information is prohibited. If you receive this in error, please contact the sender and delete or destroy this message and any copies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Gentlemen, I am indeed very grateful to you all and thank you all. There is, indeed, compelling evidence supporting the case for fewer and even no LPARs but, unfortunately, it is proprietary and cannot be presented. I know that all sounds a little too convenient, but it is true. But thank you all and rest assured I have, indeed, read and learned and appreciate very much all that you all have written and said. Please, no hard feelings. Thank you. On Fri, Mar 5, 2010 at 2:37 PM, Ted MacNEIL eamacn...@yahoo.ca wrote: I'm still kind of curious what exactly you mean by: - Performance: wasted CPU cycles especially for handshaking between LPARs doing shared I/O So am I. I haven't seen these issues since the early days of MDF and PR/SM in the 1980's. I have thoughts on what you mean by these kinds of things, but I am reserving judgement. I'm not. This sounds like a diatribe against something that has matured in the last 25 years. Rather than say it's bad because I say it's bad, present some evidence. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Just a nit. On supported IBM hardware, there is no valid argument for NO LPARs. Basic mode is not available. Even if you only have one image, it is still an LPAR. Dave Gibney Information Technology Services Washington State University -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of George Henke Sent: Friday, March 05, 2010 1:50 PM To: IBM-MAIN@bama.ua.edu Subject: Re: LPARs: More or Less? Gentlemen, I am indeed very grateful to you all and thank you all. There is, indeed, compelling evidence supporting the case for fewer and even no LPARs but, unfortunately, it is proprietary and cannot be presented. I know that all sounds a little too convenient, but it is true. But thank you all and rest assured I have, indeed, read and learned and appreciate very much all that you all have written and said. Please, no hard feelings. Thank you. On Fri, Mar 5, 2010 at 2:37 PM, Ted MacNEIL eamacn...@yahoo.ca wrote: I'm still kind of curious what exactly you mean by: - Performance: wasted CPU cycles especially for handshaking between LPARs doing shared I/O So am I. I haven't seen these issues since the early days of MDF and PR/SM in the 1980's. I have thoughts on what you mean by these kinds of things, but I am reserving judgement. I'm not. This sounds like a diatribe against something that has matured in the last 25 years. Rather than say it's bad because I say it's bad, present some evidence. - Too busy driving to stop for gas! - - For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Gentlemen, I am indeed very grateful to you all and thank you all. There is, indeed, compelling evidence supporting the case for fewer and even no LPARs but, unfortunately, it is proprietary and cannot be presented, for obvious reasons. I know that all sounds just a little too convenient, but it is true. But thank you all and rest assured I have, indeed, read and learned and appreciate very much all that you all have written and said. Please, no hard feelings. Thank you. On Fri, Mar 5, 2010 at 2:28 PM, Scott Rowe scott.r...@joann.com wrote: That's your reply? IBM owes me money? Why? Because I did my job? Now you will probably go on to say that nobody has refuted your position, right? Are you really interested in having an intelligent discussion here? You seem to just be posting long diatribes and ignoring or dismissing all the well thought out responses you receive. I'm still kind of curious what exactly you mean by: - Performance: wasted CPU cycles especially for handshaking between LPARs doing shared I/O I have thoughts on what you mean by these kinds of things, but I am reserving judgement. George Henke gahe...@gmail.com 3/5/2010 12:15 PM No, I'm saying that it's preposterous for you to say such a thing, because I do not believe it is prevalent. . . . I recently was involved in situation where management was desiring to do such a thing, through their own ignorance of the technology, but I was able to defeat it. IBM owes you money. CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
This whole thread is compelling evidence that some like to spread any nonsense they can dream up. Worth a few laughs anyway On Fri, Mar 5, 2010 at 1:55 PM, Gibney, Dave gib...@wsu.edu wrote: Just a nit. On supported IBM hardware, there is no valid argument for NO LPARs. Basic mode is not available. Even if you only have one image, it is still an LPAR. Dave Gibney Information Technology Services Washington State University -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of George Henke Sent: Friday, March 05, 2010 1:50 PM To: IBM-MAIN@bama.ua.edu Subject: Re: LPARs: More or Less? Gentlemen, I am indeed very grateful to you all and thank you all. There is, indeed, compelling evidence supporting the case for fewer and even no LPARs but, unfortunately, it is proprietary and cannot be presented. I know that all sounds a little too convenient, but it is true. But thank you all and rest assured I have, indeed, read and learned and appreciate very much all that you all have written and said. Please, no hard feelings. Thank you. On Fri, Mar 5, 2010 at 2:37 PM, Ted MacNEIL eamacn...@yahoo.ca wrote: I'm still kind of curious what exactly you mean by: - Performance: wasted CPU cycles especially for handshaking between LPARs doing shared I/O So am I. I haven't seen these issues since the early days of MDF and PR/SM in the 1980's. I have thoughts on what you mean by these kinds of things, but I am reserving judgement. I'm not. This sounds like a diatribe against something that has matured in the last 25 years. Rather than say it's bad because I say it's bad, present some evidence. - Too busy driving to stop for gas! - - For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Guy Gardoit z/OS Systems Programming -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
There is, indeed, compelling evidence supporting the case for fewer and even no LPARs but, unfortunately, it is proprietary and cannot be presented, for obvious reasons. With all due respect, BS. How can the number of LPARs be proprietort? Sniff! Sniff! I smell a cop-out. If it was a secret, why did you even engage in this discussion? S**t, or get off the pot! - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On Fri, Mar 5, 2010 at 5:04 PM, George Henke gahe...@gmail.com wrote: There is, indeed, compelling evidence supporting the case for fewer and even no LPARs but, unfortunately, it is proprietary and cannot be presented, for obvious reasons. Not obvious, at least not to me...??? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
I think I may have finally come upon a valid justification for a separate UAT, QA LPAR; maybe the only justification. You can only have one instance of Security, RACF, ACF2, TSS, in an LPAR, z/OS Domain, at any one time. Since, for QA testing, the need is to mirror PROD Security so that the security rules for a change being made are tested *before* moving the change to PROD, then there would need to be a separate LPAR to hold a separate Security DB that mirrored the PROD DB. Since the DEV LPAR already has a DEV Security DB and there can be only one instance of a Security DB per LPAR, this would preclude the mirroring of the PROD Security DB in a DEV LPAR, and is sufficient reason for creating a separate LPAR for QA, UAT, testing. Of all the justifications, presented thus far, for creating a separate LPAR for QA, UAT testing, this appears to be the only one that cannot be refuted. However, it still begs the question, why have LPARs at all, because separate Security DBs *can* be configured in separate Virtual Machines running separate instances of z/OS under z/VM without LPARs at all. On Mon, Mar 1, 2010 at 1:16 PM, Rick Fochtman rfocht...@ync.net wrote: --snip--- FORTRAN H and FORTH are two very different languages. I don't know if there was ever a FORTH implementation for OS/360. ---unsnip--- I was completely unaware of a FORTH processor/language. ---snip BTW, FORTRAN H was written in FORTRAN H, a much uglier language than BSL and its descendants. ---unsnip- Parts of the FORTRN H compiler were written in FORTRAN; other parts were written in Assembler. -- Rick -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On Thu, Mar 4, 2010 at 6:21 PM, George Henke gahe...@gmail.com wrote: However, it still begs the question, why have LPARs at all, because separate Security DBs *can* be configured in separate Virtual Machines Even with VM, there are cases where the complete isolation of LPARs is useful for testing system software (separate, real IOCP, etc.,; virtual LANs have helped a lot here). But you seem to be saying, Why use LPAR instead of z/VM? In general, z/OS shops prefer the control offered by LPAR. As a long-time VMer, I see that as heresy, but I do understand the underlying argument that says I don't have to administer PR/SM the same way I have to administer z/VM. Add to that the fact that all machines are LPAR-Mode-only now, plus the cost of z/VM, and it's a no-brainer for many. ObAnecdote: back at Linuxcare, we had a Multiprise 3000 with 2 IFLs (yeah, the only one in the world, probably -- IBM gave us a special dispensation to have 2 IFLs instead of requiring a CP). We had 4 VM LPARs on it: one DIRMAINT, one VM:Secure, one native directory handling, one for demos. And of course a boatload of Linux guests on each VM. I said, This is dumb. We have VM; we should run in Basic Mode with four VM guests and it will be better, because we'll share real memory, both processors, etc. (the demo LPAR was largely idle, as well). So we tried it. It was horrible -- on the order of 10x slower. But we had no tools to measure it and no time to fool with it, so we went back to LPAR-mode. I still wonder why it was so bad! ...phsiii -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
In general, z/OS shops prefer the control offered by LPAR. As a long-time VMer, I see that as heresy, but I do understand the underlying argument that says I don't have to administer PR/SM the same way I have to administer z/VM. And, you have one less skill set requirement! Give me a performance anayst, a sysprog, and a hardware guy. With them I can set up a multiple LPAR environment. Do it with z/VM in the mix, and I need another SYSPROG. VM MVS skills are rare to find in the same individual(s). I'm not belittling their skills. I just don't need them in a PR/SM environment. Sorry, no offense intended. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On Thu, Mar 4, 2010 at 8:39 PM, Ted MacNEIL eamacn...@yahoo.ca wrote: And, you have one less skill set requirement! Give me a performance anayst, a sysprog, and a hardware guy. With them I can set up a multiple LPAR environment. Do it with z/VM in the mix, and I need another SYSPROG. VM MVS skills are rare to find in the same individual(s). I'm not belittling their skills. I just don't need them in a PR/SM environment. Yeah, nicely put. Especially true among MVS folks, who have historically been more able to specialize in one area or another because the team was usually bigger than the VM (and now Linux) team. Again, not belittling anyone; you do what you're asked/tasked to do. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Let me get this straight: You think this is a valid argument when applied to security, but somehow thought that the same argument applied to OS maintenance/release was somehow refuted? George Henke gahe...@gmail.com 03/04/10 6:22 PM I think I may have finally come upon a valid justification for a separate UAT, QA LPAR; maybe the only justification. You can only have one instance of Security, RACF, ACF2, TSS, in an LPAR, z/OS Domain, at any one time. Since, for QA testing, the need is to mirror PROD Security so that the security rules for a change being made are tested *before* moving the change to PROD, then there would need to be a separate LPAR to hold a separate Security DB that mirrored the PROD DB. Since the DEV LPAR already has a DEV Security DB and there can be only one instance of a Security DB per LPAR, this would preclude the mirroring of the PROD Security DB in a DEV LPAR, and is sufficient reason for creating a separate LPAR for QA, UAT, testing. Of all the justifications, presented thus far, for creating a separate LPAR for QA, UAT testing, this appears to be the only one that cannot be refuted. However, it still begs the question, why have LPARs at all, because separate Security DBs *can* be configured in separate Virtual Machines running separate instances of z/OS under z/VM without LPARs at all. On Mon, Mar 1, 2010 at 1:16 PM, Rick Fochtman rfocht...@ync.net wrote: --snip--- FORTRAN H and FORTH are two very different languages. I don't know if there was ever a FORTH implementation for OS/360. ---unsnip--- I was completely unaware of a FORTH processor/language. ---snip BTW, FORTRAN H was written in FORTRAN H, a much uglier language than BSL and its descendants. ---unsnip- Parts of the FORTRN H compiler were written in FORTRAN; other parts were written in Assembler. -- Rick -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
--snip--- FORTRAN H and FORTH are two very different languages. I don't know if there was ever a FORTH implementation for OS/360. ---unsnip--- I was completely unaware of a FORTH processor/language. ---snip BTW, FORTRAN H was written in FORTRAN H, a much uglier language than BSL and its descendants. ---unsnip- Parts of the FORTRN H compiler were written in FORTRAN; other parts were written in Assembler. -- Rick -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
In 4b86e20f.20...@ync.net, on 02/25/2010 at 02:48 PM, Rick Fochtman rfocht...@ync.net said: They weren't as horrendous as all that; If I wanted a WAITR then I'd go to a restaurant. That whole PRSCB mechanism was a kludge, and when MFT II came along things were much better. you just had to pay close attention to what you were doing. What did you do about normal programs, which did WAIT rather than WAITR? Especially programs that you didn't write? FORTH (IEKAA00) FORTRAN H and FORTH are two very different languages. I don't know if there was ever a FORTH implementation for OS/360. BTW, FORTRAN H was written in FORTRAN H, a much uglier language than BSL and its descendants. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
snip Prior to MFT II and HASP II, HASP also automated the control of partitions in MFT, but I'm not going to ask you to believe just how bad the facilities were; suffice it to say that the original MFT without HASP or ASP was a nightmare. --unsnip-- They weren't as horrendous as all that; you just had to pay close attention to what you were doing. I still have (moderately fond) memories of running DSO in a 18K partition so I could use the rest of the core box for system generation. IIRC, FORTH (IEKAA00) wouldn't link in a partition smaller than 200K. Rick -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
In my previous summary of arguments thus far, I forgot to note this one: *Pro: *LPARs eliminate single points of failure. *Con:* XRC, PPRC-XD, FLASH/COPY, METRO/MIRROR, GLOBAL/ MIRROR, now provide recovery from instantaneous to anywhere around 4 hours and just effectively than LPARs, if not more, because offsite. Having LPARs for this purpose now just creates needless redundancy and expense. I came across the following from the horse's mouth itself: z/OS V1R9.0 Planning for Installation GA22-7504-17 z/OS*®* (program number 5694-A01). Some highlights of z/OS are: - The 64-bit z/Architecture™ implemented by z/OS eliminates bottlenecks associated with the lack of addressable memory. *64-bit real (central) storage support eliminates expanded storage, helps eliminate paging, and may allow you to consolidate** your current systems into fewer logical partitions (LPARs) or to a single native image.* I never considered storage fencing as a possible justification for LPARs, but maybe that is it? If so, then even that justification has now been eliminated with 64-bit central storage. It does fit the history of the evolution of operating systems. In the old MFT days, did not we have core and quite limited memory? Then that was replaced with integrated circuits which according to Moore's Law doubles every 2 years. And what happened? No more MFT, nor more partitions, but MVT, then SVS and MVS. So now that we have 64-bit addressable memory, does this presage the fading away again of partitioning, of LPARs and create an urge to merge? I am astounded and humbled at the depth and breadth of IT knowledge, intelligence, and thinking of the contributors in this trail; it is awesome. Thank you all very much. But, in Hans Christian Anderson's story, the tailors needed to be paid a lot of money because the fabric was very expensive. But, of course, only the very wise could see it. So in my sublime ignorance let me now also exclaim, The Emperor is naked. Where ignorance is bliss, tis folly to be wise (Thomas Gray) On Wed, Feb 24, 2010 at 1:33 AM, Alan Altmark alan_altm...@us.ibm.comwrote: On Tue, 23 Feb 2010 12:30:25 -0500, Scott Rowe scott.r...@joann.com wrote: I don't know that I would say that running QA in a different LPAR than DEV is best practices, I certainly run them in the same LPAR here, and at nearly every site I have ever worked at. All PCI-compliant installations (a) Must have separate DEV/TEST/QA and PRODUCTION environments (b) Must have Separation of Duties for the two environments (c) Cannot give DEV/TEST access to PRODUCTION PANs And rather than micro-manage the ACLs, it is far simpler to create another LPAR. Having done it once, you replicate your success in order to separate QA from DEV/TEST. (QA really is a different environment than DEV/TEST, IMO.) My point is that the level of separation is, more often than not, dictated not by the capabilities of the OS, but by (1) regulatory considerations (2) in-house politics (appl owner, security, turf wars, ...) (3) system programmer convenience I certainly have no desire to spend time on VM if I don't need the functionality, I simply don't have the time. I have worked on VM before, and rather like it, but if the tool doesn't fit I have no desire to use it. That's the real nugget of Truth. Do what you need to do. Just do it with your eyes wide open and use the right tool for the job. Alan Altmark z/VM Development IBM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
In b53f38421002230756r50f66628r28ec6b31bfc9d...@mail.gmail.com, on 02/23/2010 at 10:56 AM, George Henke gahe...@gmail.com said: Intelligent people can disagree and still be friends. But they don't misrepresent their friends' positions. but I do know we can do better than just LPARs for the sake of LPARs. I saw nobody advocating LPARs for the sake of LPARs. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
In m3ocjfgadq@garlic.com, on 02/23/2010 at 11:55 AM, Anne Lynn Wheeler l...@garlic.com said: some 370s did have a sort of virtual memory (a little analogous to current LPARs) ... used for emulators The implementation of the DOS Emulator Feature on the 3145 involved an associative memory. I couldn't explain it in any way that didn't involve planned support for paging. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
In 1266942295.28704.243.ca...@chuck.duda.com, on 02/23/2010 at 11:24 AM, David Andrews d...@lists.duda.com said: One of you Old Ones (and I'm thinking of Shmuel in particular) correct me on this, but didn't bare MVT have a horrendous core fragmentation issue? VMS[1] had a horrendous core fragmentation issue; for MVT is was less severe. My poor recollection is that HASP initiators essentially reintroduced partitions to MVT to help beat that problem. No, But it did eliminate the need for multiple Reader and Writer regions. Also, the execution batch facility helped alleviate the problem. Prior to MFT II and HASP II, HASP also automated the control of partitions in MFT, but I'm not going to ask you to believe just how bad the facilities were; suffice it to say that the original MFT without HASP or ASP was a nightmare. [1] No connection to the DEC operating system for the VAX. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On Wed, 24 Feb 2010 10:50:02 -0500, George Henke gahe...@gmail.com wrote: I never considered storage fencing as a possible justification for LPARs, but maybe that is it? If so, then even that justification has now been eliminated with 64-bit central storage. George, you keep looking at the speeds feeds to determine whether or not multiple partitions are necessary. It isn't technology that drives that decision. (see my prior post) Then that was replaced with integrated circuits which according to Moore's Law doubles every 2 years. And what happened? No more MFT, nor more partitions, but MVT, then SVS and MVS. IThe more memory you put on the box, the more memory gets used to hold the description of all that memory (metadata). The more demand for memory you put on the box, the more often the OS has to touch metadata and the more of it has to be touched. There are mitigating technologies, but even so there is a point of diminishing returns on memory size. It gets simpler and cheaper to just say create another instance of the OS and split your workload. So now that we have 64-bit addressable memory, does this presage the fading away again of partitioning, of LPARs and create an urge to merge? Same answer. Alan Altmark z/VM Development IBM Endicott -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
In b53f38421002191505j1b5fece8q2535a56965763...@mail.gmail.com, on 02/19/2010 at 06:05 PM, George Henke gahe...@gmail.com said: No, you get to ask how many CICSes or DB2s or whatever do I need all running under the same or fewer or 1 z/OS virtual machine. How does that differ depending on PR/SM versus z/VM? Precisely the point. You know of any lightly loaded boxes lately? Yes. What isolation? Isolation of DASD. Isolation of service being tested. Isolation of program products with wonky licenses. Unless you want an administrative nightmare or have an army of system programmers, you will follow IBM's strong recommendation to share everything as much as possible: SHARED PARMLIB, SHARED MASTERCAT, SHARED PROCLIB, SHARED JESPOOL. That's my preference for everything but DR; auditors, legal and management don't always agree. After setting all that up, blow away just one system symbolic and see how much isolation you really have. I've seen plenty of shared failure modes, but not that one. Perhaps there's something about your shop that makes it more likely, but elsewhere it's rare. I'd be a lot more worried about losing the shared master catalog, which is also rare. Show me 1 shop running a SFW sandbox, Combined DEV/QA, PROD, DR LPAR configuration who will pay less by splitting QA into a separate LPAR. First show me where I said that they would in the specific case. You raised a general objection against the use of PR/SM, and I addressed it as a general issue. How about counting and comparing the instruction path length of each. Why would I do that when it has nothing to do with my question? Path length is not robustness. True. But it does not predate SVS, VS1, MVT, MFT, and OS Rel 17 from which (except for VS1) MVS evolved. It certainly predates OS/VS1 and OS/VS2 SVS. I don't recall the exact date for OS/360 Release 17, but Release 14 was out in 1968, so CP/67 was out first. Virtual Machine Facility/370 was just the next version of CP/67. Furthermore, a duck is still a duck no matter what you do to it, Claiming that doesn't make it true. but no matter what you do to it, it still just a hypervisor as one of the links included by some of the creators of PR/SM in the trail notes pointing out that PR/SM is now officially referred to as the LPAR Hypervisor. The fact that PR/SM doesn't offer most of the VM facilities doesn't mean that z/VM doesn't. After sharing everything, One of the reasons for isolation is that you are not always allowed to share. as previously noted, All that you noted was that it was possible to configure shared resources with a single point of failure, not that the failure was likely. If you seriously believe z/VM is larger, more robust with more functionality than z/OS, then you really need to take a another look. If you seriously believe that you are accurately reflecting either what I believe or what I have written, then you need to take another look. I never claimed that z/VM was larger or more robust; I simply asked you to provide data to justify your claim that MVS was more robust. I neither mentioned size nor took a position on robustness. As to functionality, each has something that the other is missing. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Peace, Shmuel, nol contende. Intelligent people can disagree and still be friends. This whole brainstorming exercise started when my client, who is relatively small, questioned a very specific thing, basically: Why would I NOT keep QA in the same LPAR with DEV. Why create a new LPAR just for QA and incur $6 million of additional software costs. My knee-jerk reaction, of course, was, Because everyone is doing it and it is 'best practices'. But it immediately became apparent how ridiculous that logic or lack thereof was. And the more I tried to find a justification, a good reason, for not defying this best practice, the more I could not find one. And when I could not, I started questioning the merits of having LPARs at all and opened the question here with the hope that someone could. And so far there does not appear to be any. To summarize, thus far it has been argued: *Pro:* z/VM in microcode is more efficient. *Con:* Those efficiencies quickly disappear and are more than offset by the additional CP overhead incurred by the cross LPAR handshaking that must occur for shared I/O. Please see Cheryl Watson's newsletters on this. She points this out and elaborates on it. *Pro:* You can isolate workloads better and give customers and clients better isolation and security. There may also be requirements mandated by law. *Con:* But that isolation is seriously compromised when after creating a separate LPAR, it is all tied back together with shared SYSRES, SYSCAT, PARMLIB, PROCLIB, JESPOOL for support, when best practices call for sharing everything at the system level as much as possible? Indeed, one of the vital functions system symbolics performs is to allow for this sharing, particularly in PARMLIB. True there are times when there should be a chinese wall built around certain sensitive workloads and then LPAR is certainly needed. But these is more often the exception, than the rule. *Pro:* The complexity of knowing both z/VM and z/OS makes it too hard to find people who know both. *Con:* Having installed both in total more than a dozen times myself, the latest being z/VM 5.4 last November, and having known and worked with sooo many others far more knowledgeable than I, not to mention the competition at interview time for both these skill sets, this is simply not true. *Pro:* With LPARs it is possible to take advantage of IBM's sub-capacity pricing algorithm and save millions. *Con:* Yes, indeed. IBM's sub-capacity pricing algorithm encourages it. But is this necessarilly something we should be encouraged to be doing, ie proliferating z/OS otherwise needlessly, carving up memory, just to take advantage of a favorable pricing algorithm. Are we being led down the primrose path? I like to think that, as a general rule, a software solution will always beat a hardware solution operationally, economically, and financially. But with PR/SM the trend seems to be in the other direction. Such a policy might favor IBM and ISVs, and with IBM's sub-capacity pricing algorithm, it might even favor us in the short-run, but in the long-run it is making us more dependent on and constrained by the hardware, not less, and so is sub-optimal. It is all somewhat reminiscent of the old MFT days when everything ran in partitions. There were all kinds of inefficiencies introduced when we ran things in fixed partitions then. Certain jobs could not start because they needed a certain amount of memory, devices or system datasets were not available in certain partitions. When MVT came along it removed those constraints and voila, suddenly the floodgates of the CPU and system were open for work and it has remained that way through SVS, MVS, until PR/SM came along. And now we seem to be back into the old MFT partition mode once again all in the name of best practices. As Marie Antoinette said as she stood before a statute of liberty erected by the guillotine, Liberty what crimes are committed in thy name (Mary Baker Eddy) As I said at the start, this is just brainstorming and I do not know the answer, but I do know we can do better than just LPARs for the sake of LPARs. On Mon, Feb 22, 2010 at 7:32 PM, Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net shmuel%2bibm-m...@patriot.net wrote: In b53f38421002191505j1b5fece8q2535a56965763...@mail.gmail.com, on 02/19/2010 at 06:05 PM, George Henke gahe...@gmail.com said: No, you get to ask how many CICSes or DB2s or whatever do I need all running under the same or fewer or 1 z/OS virtual machine. How does that differ depending on PR/SM versus z/VM? Precisely the point. You know of any lightly loaded boxes lately? Yes. What isolation? Isolation of DASD. Isolation of service being tested. Isolation of program products with wonky licenses. Unless you want an administrative nightmare or have an army of system programmers, you will follow IBM's strong recommendation to share everything as much as possible: SHARED PARMLIB,
Re: LPARs: More or Less?
On Mon, 22 Feb 2010 13:19:37 -0500, Anne Lynn Wheeler l...@garlic.com wrote: The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. gahe...@gmail.com (George Henke) writes: Yes, I believe it was some how connected to Preferred Machine Assist (PMA) where page 0 was actually owned by MVS not VM. preferred machine assist could be considered step on the way to LPARs ... since part of it involved the virtual machine pages being mapped to fixed real storage. the earlier version of this (preferred V=R guest) had been done for vm370 at the science center circa mid-70s on a csc/vm base. There was then a joint study with ATT ... -SNIP-- At Monsanto Europe in Brussels about 1976 I wrote some mods to VM/370 to defeat Shadow Page Tables for V=R machines so we could run MVS under VM/370 without a crippling overhead. I sent that code out into the world on some (Waterloo?) VM Mods tape, but my own copy got dumped in some move down the years. Wish I had it now, it would go really nicely on Herc. DC -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On Tue, 2010-02-23 at 10:56 -0500, George Henke wrote: It is all somewhat reminiscent of the old MFT days when everything ran in partitions. There were all kinds of inefficiencies introduced when we ran things in fixed partitions then. [...] When MVT came along it removed those constraints One of you Old Ones (and I'm thinking of Shmuel in particular) correct me on this, but didn't bare MVT have a horrendous core fragmentation issue? My poor recollection is that HASP initiators essentially reintroduced partitions to MVT to help beat that problem. -- David Andrews A. Duda and Sons, Inc. david.andr...@duda.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. d...@lists.duda.com (David Andrews) writes: One of you Old Ones (and I'm thinking of Shmuel in particular) correct me on this, but didn't bare MVT have a horrendous core fragmentation issue? My poor recollection is that HASP initiators essentially reintroduced partitions to MVT to help beat that problem. especially for long running jobs. Boeing huntsville had installed duplex (2-processor SMP) 360/67 for tss/360 ... when tss/360 ran into deelivery problems ... they would run it as two (partitioned) 360/65s under os/360. Their workload was long-running 2250 (vector graphics) design applications which had enormous storage fragmentation issues. To address that they modified MVT (release 13) to build 360/67 page tables and run in virtual memory mode ... there was no paging faults or page i/o supported ... the virtual memory mode was just used as countermeasure to the significant storage fragmentation problem (using virtual address tables to re-arrange memory addresses to be contiguous). Later I was brought in for a summer at boeing seattle as part of setting up BCS (boeing computer services) ... and put in at cp67 360/67 (simplex) in the 360/30 datacenter at corporate hdqtrs (beoing field) ... at primarily been used for corporate payroll. That summer, the 2-processor 360/67 was also moved to Seattle from Huntsville. When 370 was initially announced, there was no virtual memory support ... and one of the IBM SEs on the boeing account wondered what was the (virtual machine virtual memory) cp67 path in 370. some 370s did have a sort of virtual memory (a little analogous to current LPARs) ... used for emulators ... which was a mode that a base/bound flavor of (contiguous) virtual memory (i.e. virtual memory up to the bound limit and all addresses were relocated by the base value). The boeing account SE did a hack to cp67 that used the base/bound on 370s (pre virtual memory) ... didn't do paging but would swap in/out whole virtual machine address space. also, somewhat analogous to the preferred v=r guest ... recent reference (in the v=r case, the addresses were contiguous and the virtual address was same as the real address): http://www.garlic.com/~lynn/2010d.html#79 LPARs: More or Less? a few recent posts mentioning BCS, boeing huntsville, etc: http://www.garlic.com/~lynn/2010c.html#89 Notes on two presentations by Gordon Bell ca. 1998 http://www.garlic.com/~lynn/2010c.html#90 Notes on two presentations by Gordon Bell ca. 1998 http://www.garlic.com/~lynn/2010c.html#91 Notes on two presentations by Gordon Bell ca. 1998 http://www.garlic.com/~lynn/2010d.html#29 search engine history, was Happy DEC-10 Day http://www.garlic.com/~lynn/2010d.html#76 Senior Java Developer vs. MVS Systems Programmer (warning: Conley rant) -- 42yrs virtualization experience (since Jan68), online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. dcartwri...@ymail.com (David Cartwright) writes: At Monsanto Europe in Brussels about 1976 I wrote some mods to VM/370 to defeat Shadow Page Tables for V=R machines so we could run MVS under VM/370 without a crippling overhead. I sent that code out into the world on some (Waterloo?) VM Mods tape, but my own copy got dumped in some move down the years. Wish I had it now, it would go really nicely on Herc. re: http://www.garlic.com/~lynn/2010d.html#79 LPARs: More or Less? the stuff done on csc/vm ... that leaked out to att, had been about the same time ... slightly eariler. the design of the shadow page tables followed the semantics for the hardware look-aside buffer. the virtual machine has page tables that translate virtual addresses to what it thinks are real addresses. However, these are actually virtual addresses for the virtual machine. So when VM runs a virtual machine ... in virtual memory mode ... it is actually run with shadow page tables. Shadow page table entries start out all invalid. The virtual machine immediately page faults, vm then has to look at the (virtual) page tables (in virtual machine) to translate from the virtual memory address to the virtual machine address ... vm then looks it its page table to translate from the virtual machine address to the real machine address. It is this real machine address that is placed into the shadow tables. The early, low mid range 370s had a single STO stack ... everytime there was a change in the virtual address space pointer ... the hardware lookaside buffer was cleared and all entries invalidated. Early VM370's shadow table operation had similar design, single STO stack, everytime the virtual machine changed virtual address space pointer, all the shadow page table entries were cleared and invalidated. Moving from SVS to MVS significantly aggrevated this ... because MVS was changing virtual address space pointer at the drop of the hat (and vm370 was going thru massive overhead constantly invalidating the shadow page tables everytime MVS reloaded CR1). 370/168 had a 7-entry STO stack. There was a seven entry LRU queue of the most recently used STO values. Each hardware look-aside buffer entry had a 3-bit tag ... it was either one of the 7 currently valid STO entries ... or invalid. MVS constant reloading/changing CR1 was mitigated on real 168 with the 7-entry STO stack (loading new value into CR1 didn't do anything if the value was already one of the seven values in the STO staok). It wasn't until vm370 release 5 with HPO option that vm370 finally shipped something equivalent to multiple STO-stack (i.e. multiple shadow page tables being kept for a single virtual machine ... to try and minimize having to constantly clear all shadow page table entries every time MVS fiddled with CR1). The demise of FS saw a big need to get products back into the 370 product pipeline quickly. 3033 was such effort ... take the 370/168 logic and remap it to slightly faster chips. There was also some activity to introduce some purely MVS microcode performance assists on 3033 ... one such involved cross-memory services. One of the issues with 3033 and cross-memory services ... was the 3033 still had the 370/168 design with 7-entry STO stack ... and cross-memory services was significantly increasing the number of STOs being used ... overrunning the seven entries ... with corresponding big increase in look-aside buffer entry flushing (which netted out to worse performance; somewhat analogous to the shadow page table flushing that VM was constantly being forced to do). -- 42yrs virtualization experience (since Jan68), online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On Tue, 23 Feb 2010 10:56:19 -0500, George Henke wrote: ... my client, who is relatively small, questioned a very specific thing, basically: Why would I NOT keep QA in the same LPAR with DEV. Why create a new LPAR just for QA and incur $6 million of additional software costs. Good question. Your experience with this seems to differ from others who have responded. Do you really expect to incur this additional software cost? Have you analyzed the reasons for it? My knee-jerk reaction, of course, was, Because everyone is doing it and it is 'best practices'. best practices? Says who? I started questioning the merits of having LPARs at all and opened the question here with the hope that someone could. And so far there does not appear to be any. To summarize, thus far it has been argued: *Pro:* z/VM in microcode is more efficient. To pick a nit, there is no microcode on a z9 or z10. There is millicode, which is quite unlike microcode. PR/SM is likely more efficient than z/VM because it doesn't do nearly as much. If you had a z/VM that supported only V=R guests and dedicated devices it might be just as efficient as PR/SM. *Pro:* You can isolate workloads better and give customers and clients better isolation and security. There may also be requirements mandated by law. *Con:* But that isolation is seriously compromised when after creating a separate LPAR, it is all tied back together with shared SYSRES, SYSCAT, PARMLIB, PROCLIB, JESPOOL for support, when best practices call for sharing everything at the system level as much as possible? If you share everything then you are not isolating anything. Sharing PARMLIBs, PROCLIBs, SYSRES, SPOOL and master catalog between LPARs does not make you any more vulnerable than running a single LPAR Again with the best practices? I don't think anyone has used the phrase in this thread except for you. I don't like the term. It seems to me that people like to use it to claim that their way is the best. *Pro:* With LPARs it is possible to take advantage of IBM's sub-capacity pricing algorithm and save millions. *Con:* Yes, indeed. IBM's sub-capacity pricing algorithm encourages it. You started by saying that a new LPAR was going to cost you $6 million. In your case, will it save you money or cost more? I like to think that, as a general rule, a software solution will always beat a hardware solution operationally, economically, and financially. Is that based upon intuition or analysis? I do agree that a single well-defined WLM environment will perform better than multiple ones. But with PR/SM the trend seems to be in the other direction. Such a policy might favor IBM and ISVs, and with IBM's sub-capacity pricing algorithm, it might even favor us in the short-run, but in the long-run it is making us more dependent on and constrained by the hardware, not less, and so is sub-optimal. I don't follow your logic. How does using PR/SM make you more dependent on z/Architecture to run z/OS? -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
George, I don't know that I would say that running QA in a different LPAR than DEV is best practices, I certainly run them in the same LPAR here, and at nearly every site I have ever worked at. In small shops I typically run a production LPAR, a non-production LPAR (DEV, QA, etc), and a Sysprog Sandbox LPAR. As others have said, if you run everything in one LPAR, you are not going to have any process for installing and testing new OS and/or ISP software before going production. This also allows you to control CPU/memory usage at a high level, and prevent non-prod workloads from stealing these resources from production. Larger shops may very well not use LPAR in this way, since they may be able to justify separate CECs for non-production work. As others have mentioned, the point of isolation may be more about memory isolation than the points you are making re: SYSRES, PROCLIB, PARMLIB, etc. If the LPARs are for different clients, then I can certainly understand the need for separate LPARs, since an APF authorized program could easily spy into another address space in the same LPAR, but doing that across LPARs is a whole 'nother ball o' wax. All in all, I think your arguments for VM over LPAR are way off-base. Most sites have little or no need for the added capabilities in VM, LPAR does the job very well, and at a significantly lower level of effort and complexity - even if you ignore the addition costs of VM (memory, storage, overhead, and of course acquisition/maintenance). I certainly have no desire to spend time on VM if I don't need the functionality, I simply don't have the time. I have worked on VM before, and rather like it, but if the tool doesn't fit I have no desire to use it. George Henke gahe...@gmail.com 2/23/2010 10:56 AM Peace, Shmuel, nol contende. Intelligent people can disagree and still be friends. This whole brainstorming exercise started when my client, who is relatively small, questioned a very specific thing, basically: Why would I NOT keep QA in the same LPAR with DEV. Why create a new LPAR just for QA and incur $6 million of additional software costs. My knee-jerk reaction, of course, was, Because everyone is doing it and it is 'best practices'. But it immediately became apparent how ridiculous that logic or lack thereof was. And the more I tried to find a justification, a good reason, for not defying this best practice, the more I could not find one. And when I could not, I started questioning the merits of having LPARs at all and opened the question here with the hope that someone could. And so far there does not appear to be any. To summarize, thus far it has been argued: *Pro:* z/VM in microcode is more efficient. *Con:* Those efficiencies quickly disappear and are more than offset by the additional CP overhead incurred by the cross LPAR handshaking that must occur for shared I/O. Please see Cheryl Watson's newsletters on this. She points this out and elaborates on it. *Pro:* You can isolate workloads better and give customers and clients better isolation and security. There may also be requirements mandated by law. *Con:* But that isolation is seriously compromised when after creating a separate LPAR, it is all tied back together with shared SYSRES, SYSCAT, PARMLIB, PROCLIB, JESPOOL for support, when best practices call for sharing everything at the system level as much as possible? Indeed, one of the vital functions system symbolics performs is to allow for this sharing, particularly in PARMLIB. True there are times when there should be a chinese wall built around certain sensitive workloads and then LPAR is certainly needed. But these is more often the exception, than the rule. *Pro:* The complexity of knowing both z/VM and z/OS makes it too hard to find people who know both. *Con:* Having installed both in total more than a dozen times myself, the latest being z/VM 5.4 last November, and having known and worked with sooo many others far more knowledgeable than I, not to mention the competition at interview time for both these skill sets, this is simply not true. *Pro:* With LPARs it is possible to take advantage of IBM's sub-capacity pricing algorithm and save millions. *Con:* Yes, indeed. IBM's sub-capacity pricing algorithm encourages it. But is this necessarilly something we should be encouraged to be doing, ie proliferating z/OS otherwise needlessly, carving up memory, just to take advantage of a favorable pricing algorithm. Are we being led down the primrose path? I like to think that, as a general rule, a software solution will always beat a hardware solution operationally, economically, and financially. But with PR/SM the trend seems to be in the other direction. Such a policy might favor IBM and ISVs, and with IBM's sub-capacity pricing algorithm, it might even favor us in the short-run, but in the long-run it is making us more dependent on and constrained by the hardware, not less, and so is
Re: LPARs: More or Less?
On Tue, 23 Feb 2010 11:24:55 -0500, David Andrews wrote: didn't bare MVT have a horrendous core fragmentation issue? Suppose that you have a 768K machine and the memory is mapped like this (I'm making up these numbers, and I don't remember where everything was located): 0-200K Nucleus 200K-600K 600K-640K SQA and CSA 640K-768K LPA All your initiators run in the area from 200K to 600K. Suppose you start a job that needs 110K. It gets the area from 200K to 310K. While that job is running, you start another job that needs 200K. It will reside from 310K to 510K. After the first job ends, there is a total of 200K available, but it is not contiguous. You can run a job that needs 110K and one that needs 90K, but nothing larger. At the MVT shop where I worked, we had a fixed number of initiators that each had their assigned Job classes. To ensure that storage would not be fragmented, we had region size standards for each job class, and all job classes for a particular initiator were required to use the same region. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Tom Marchant Sent: Tuesday, February 23, 2010 11:41 AM To: IBM-MAIN@bama.ua.edu Subject: Re: LPARs: More or Less? On Tue, 23 Feb 2010 11:24:55 -0500, David Andrews wrote: didn't bare MVT have a horrendous core fragmentation issue? Suppose that you have a 768K machine and the memory is mapped like this (I'm making up these numbers, and I don't remember where everything was located): 0-200K Nucleus 200K-600K 600K-640K SQA and CSA 640K-768K LPA All your initiators run in the area from 200K to 600K. Suppose you start a job that needs 110K. It gets the area from 200K to 310K. While that job is running, you start another job that needs 200K. It will reside from 310K to 510K. After the first job ends, there is a total of 200K available, but it is not contiguous. You can run a job that needs 110K and one that needs 90K, but nothing larger. At the MVT shop where I worked, we had a fixed number of initiators that each had their assigned Job classes. To ensure that storage would not be fragmented, we had region size standards for each job class, and all job classes for a particular initiator were required to use the same region. -- Tom Marchant I remember that we had a cheat in MVT. We had an RYO tp monitor. Somebody, before my time, made a mod to GETMAIN so that a request for a ODD sized REGION would get the storage from the high end of free storage. We ran the tp monitor with an ODD region size so that it always ran high and so did not get in the way of batch regions. This place, Braniff Airways, actually ran MVT without HASP because HASP cost too much in resource. Very strange place to work. Job sysout was always directed to tape. Then the operators had a tape to print STC which could do forward and backward spacing via the console. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On Tue, 23 Feb 2010 12:30:25 -0500, Scott Rowe scott.r...@joann.com wrote: I don't know that I would say that running QA in a different LPAR than DEV is best practices, I certainly run them in the same LPAR here, and at nearly every site I have ever worked at. All PCI-compliant installations (a) Must have separate DEV/TEST/QA and PRODUCTION environments (b) Must have Separation of Duties for the two environments (c) Cannot give DEV/TEST access to PRODUCTION PANs And rather than micro-manage the ACLs, it is far simpler to create another LPAR. Having done it once, you replicate your success in order to separate QA from DEV/TEST. (QA really is a different environment than DEV/TEST, IMO.) My point is that the level of separation is, more often than not, dictated not by the capabilities of the OS, but by (1) regulatory considerations (2) in-house politics (appl owner, security, turf wars, ...) (3) system programmer convenience I certainly have no desire to spend time on VM if I don't need the functionality, I simply don't have the time. I have worked on VM before, and rather like it, but if the tool doesn't fit I have no desire to use it. That's the real nugget of Truth. Do what you need to do. Just do it with your eyes wide open and use the right tool for the job. Alan Altmark z/VM Development IBM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On Sat, 20 Feb 2010 07:16:18 -0600, Eric Bielefeld wrote: ... Also, what about z/OS's running of Unix. Isn't that kind of like running another operating system underneath it? No. z/OS doesn't run Unix underneath it. Rather, the Unix API's are incorporated in z/OS. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
In a message dated 2/22/2010 7:16:52 A.M. Central Standard Time, m42tom-ibmm...@yahoo.com writes: No. z/OS doesn't run Unix underneath it. Rather, the Unix API's are incorporated in z/OS. It may be in some old SHARE presentations, but Multi-system's Test used to run VM under MVS and more MVS's under VM according to Peter B. Saergant. The purpose was to drive the hardware as hard as possible and see how it recovered in various scenarios. There was also a CMS under MVS( Sam Lapore, RATSO SHARE Project), internal CLIST compiler(CLIQ) that's still on the shelf in Armonk for 'Marketing Reasons'. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
It may be in some old SHARE presentations, but Multi-system's Test used to run VM under MVS and more MVS's under VM according to Peter B. Yes, I believe it was some how connected to Preferred Machine Assist (PMA) where page 0 was actually owned by MVS not VM. This was to facilitate performance for VM/MVS shops because there was no comparable VM/VSE feature for MVS and VM to control the handshaking between the two The entire MVS virtual machine would get swapped out whenever an MVS address space, eg TSO user, batch, was swapped out. The handshaking issues have since been resolved by later versions of VM and/or MVS and the two now coexist fairly well. I did not mean to touch off a debate, however delightful, with my glittering generality as to what constitutes a true operating system. It was just from the little I can tell, as an outsider, that in the one-upsmanship operating system battle, VM still controls page 0, though there have been momentary lapses like PMA in the past, and whoever controls page 0 wins. On Mon, Feb 22, 2010 at 10:00 AM, Ed Finnell efinnel...@aol.com wrote: In a message dated 2/22/2010 7:16:52 A.M. Central Standard Time, m42tom-ibmm...@yahoo.com writes: No. z/OS doesn't run Unix underneath it. Rather, the Unix API's are incorporated in z/OS. It may be in some old SHARE presentations, but Multi-system's Test used to run VM under MVS and more MVS's under VM according to Peter B. Saergant. The purpose was to drive the hardware as hard as possible and see how it recovered in various scenarios. There was also a CMS under MVS( Sam Lapore, RATSO SHARE Project), internal CLIST compiler(CLIQ) that's still on the shelf in Armonk for 'Marketing Reasons'. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. gahe...@gmail.com (George Henke) writes: This was to facilitate performance for VM/MVS shops because there was no comparable VM/VSE feature for MVS and VM to control the handshaking between the two The entire MVS virtual machine would get swapped out whenever an MVS address space, eg TSO user, batch, was swapped out. it wasn't that the MVS virtual machine got swapped, when there was a virtual machine page fault; it was that the virtual machine was non-dispatchable (didn't execute) while the (virtual machine) page fault was being serviced. the issue with VM/VS1 handshaking (actually there had been a earlier implementation at univ. with MVT handshaking) was when the virtual machine had a page fault ... the virtual machine was made non-executable while the page fault was being serviced. Part of VS1 (and earlier MVT) handshaking ... was there was one-for-one mapping between VS1 page and the virtual machine page (in VS1 case, VS1 had single virtual address space ... somewhat like SVS ... and in handshaking, there was a one-for-one mapping between the VS1 virtual address space definition and the virtual machine address space). In any case, since all virtual pages appeared to be resident and VS1 would never have its own page fault. In any case, the virtual machine could have a page fault (at the VM level) and be non-executable while the page fault was being handled. The VM/VS1 handshaking would reflect a psuedo (virtual machine) page fault to the VS1 operating system ... allowing VS1 to task switch to some other task (in VS1). If there was nothing else to execute ... then VS1 would enter wait-state ... until VM had serviced the page fault (aka there was not swapping ... it was just whether the virtual machine was dispatchable or not). This allowed the virtual guest to have a higher degree of multitasking (virtual guest overlapping execution of other tasks while VM serviced a page fault). Part of the issue was that VM performed paging operations significantly more efficiently than VS1 (I had done much shorter pathlength as well as a better page replacement algorithm) ... and so VS1 could have higher thruput in virtual machine environment (once handshaking allowed VS1 to continue to execute while VM was servicing a page fault). There were other issues with virtual memory paging operations. VM's page replacement algorithm tends to approximate LRU (least recently used). Most of the guest operating systems (when they are doing paging) also tend to have page replacement algorithm that approximates LRU. There is a pathelogical scenario if both the virtual guest is taking page faults and VM is taking page faults ... that VM will select a virtual guest page that currently isn't be used (LRU) to be replaced ... and the same time that the virtual guest (possibly MVS) has decided that it wants to use that corresponding page (since it also decides that the current contents of the page isn't being used). The line I used is LRU algorithms tend not to be recursively friendly (i.e. running an virtual LRU algorithm in a virtual machine environment running an LRU algorithm can result in exactly the wrong page being chosen). misc. past posts about page replacement algorithms http://www.garlic.com/~lynn/subtopic.html#wsclock Another piece of trivia ... in the original transition from MVT to SVS and their page replacement algorithm ... I got into argument that they were doing some tweaks to their implementation that would do exactly the wrong thing. That implementation continued well into the MVS release cycle ... when it finally dawned on them that they would select high-use, shared, R/O linkpak pages for replacement before lower-use, private, R/W data pages. Originally (VS1) handshaking was in the time-frame when Endicott had also done the VM ECPS microcode assist for 138/148 ... and was trying to convince the corporation that 138/148 (and later 43xx) would be shipped as VM-only machines (somewhat like LPAR capability is shipped on all machines today). Unfortunately, at the same time POK was trying to convince corporate that vm370 should be killed off (in part because POK wanted all the people in the vm370 development group to be moved to POK to support MVS/XA development) ... so corporate never agreed to 138/148 being vm-only. old post about methology used for creating ECSP microcode assist: http://www.garlic.com/~lynn/94.html#21 370 ECPS VM microcode assist the basis guideline was that we were told that the machines had 6kbytes of microcode space available ... and to choose the pieces that would give the biggest bang-for-the-buck. E was the low-end/mid-range architecture ... analogous to XA architecture that POK had done (primarily for MVS) ... old email ref Date: 09/16/82 08:31:14 From: wheeler re: e-architecture; E-architecture is the internal name for the 370 architecture
Re: LPARs: More or Less?
Once again, thank you once again Anne and Lynn, and Mike Myers too. Nice to hear from you again, Mike. Only wished I knew all this back when we were trying to figure out how things worked. If only IBM would have made people like you available to the outside world. We had to read between the lines and that does not always yield the best results. On Mon, Feb 22, 2010 at 11:46 AM, Anne Lynn Wheeler l...@garlic.comwrote: The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. gahe...@gmail.com (George Henke) writes: This was to facilitate performance for VM/MVS shops because there was no comparable VM/VSE feature for MVS and VM to control the handshaking between the two The entire MVS virtual machine would get swapped out whenever an MVS address space, eg TSO user, batch, was swapped out. it wasn't that the MVS virtual machine got swapped, when there was a virtual machine page fault; it was that the virtual machine was non-dispatchable (didn't execute) while the (virtual machine) page fault was being serviced. the issue with VM/VS1 handshaking (actually there had been a earlier implementation at univ. with MVT handshaking) was when the virtual machine had a page fault ... the virtual machine was made non-executable while the page fault was being serviced. Part of VS1 (and earlier MVT) handshaking ... was there was one-for-one mapping between VS1 page and the virtual machine page (in VS1 case, VS1 had single virtual address space ... somewhat like SVS ... and in handshaking, there was a one-for-one mapping between the VS1 virtual address space definition and the virtual machine address space). In any case, since all virtual pages appeared to be resident and VS1 would never have its own page fault. In any case, the virtual machine could have a page fault (at the VM level) and be non-executable while the page fault was being handled. The VM/VS1 handshaking would reflect a psuedo (virtual machine) page fault to the VS1 operating system ... allowing VS1 to task switch to some other task (in VS1). If there was nothing else to execute ... then VS1 would enter wait-state ... until VM had serviced the page fault (aka there was not swapping ... it was just whether the virtual machine was dispatchable or not). This allowed the virtual guest to have a higher degree of multitasking (virtual guest overlapping execution of other tasks while VM serviced a page fault). Part of the issue was that VM performed paging operations significantly more efficiently than VS1 (I had done much shorter pathlength as well as a better page replacement algorithm) ... and so VS1 could have higher thruput in virtual machine environment (once handshaking allowed VS1 to continue to execute while VM was servicing a page fault). There were other issues with virtual memory paging operations. VM's page replacement algorithm tends to approximate LRU (least recently used). Most of the guest operating systems (when they are doing paging) also tend to have page replacement algorithm that approximates LRU. There is a pathelogical scenario if both the virtual guest is taking page faults and VM is taking page faults ... that VM will select a virtual guest page that currently isn't be used (LRU) to be replaced ... and the same time that the virtual guest (possibly MVS) has decided that it wants to use that corresponding page (since it also decides that the current contents of the page isn't being used). The line I used is LRU algorithms tend not to be recursively friendly (i.e. running an virtual LRU algorithm in a virtual machine environment running an LRU algorithm can result in exactly the wrong page being chosen). misc. past posts about page replacement algorithms http://www.garlic.com/~lynn/subtopic.html#wsclock Another piece of trivia ... in the original transition from MVT to SVS and their page replacement algorithm ... I got into argument that they were doing some tweaks to their implementation that would do exactly the wrong thing. That implementation continued well into the MVS release cycle ... when it finally dawned on them that they would select high-use, shared, R/O linkpak pages for replacement before lower-use, private, R/W data pages. Originally (VS1) handshaking was in the time-frame when Endicott had also done the VM ECPS microcode assist for 138/148 ... and was trying to convince the corporation that 138/148 (and later 43xx) would be shipped as VM-only machines (somewhat like LPAR capability is shipped on all machines today). Unfortunately, at the same time POK was trying to convince corporate that vm370 should be killed off (in part because POK wanted all the people in the vm370 development group to be moved to POK to support MVS/XA development) ... so corporate never agreed to 138/148 being vm-only. old post about methology used for creating ECSP microcode assist:
Re: LPARs: More or Less?
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. gahe...@gmail.com (George Henke) writes: Yes, I believe it was some how connected to Preferred Machine Assist (PMA) where page 0 was actually owned by MVS not VM. preferred machine assist could be considered step on the way to LPARs ... since part of it involved the virtual machine pages being mapped to fixed real storage. the earlier version of this (preferred V=R guest) had been done for vm370 at the science center circa mid-70s on a csc/vm base. There was then a joint study with ATT ... which was provided a copy of the (complete) system. One of the enhancements that ATT put into vm370 kernel was support for virtual devices operating over network (could mount a tape in one datacenter and read it from a different machine in a different datacenter). It somewhat propogated around internal ATT ... where they made some number of enhancements and migrated the source code to new machines as they came out. In the 80s, the ATT national marketing rep tracked me down about possibly helping ATT move off the platform. The csc/vm base they had didn't include SMP/multiprocessor support ... and the 3081 strategy was still multiprocessor only ... before TPF customers forced the company into doing 3083 uniprocessor (at the time, TPF still didn't have multiprocessor support). ATT was being forced to going with clone processor vendor that had single processor products (for the again vm370 system). That old csc/vm system included my dynamic adaptive resource manager ... so I made a point of it being able to dynamically adapt across a broad range of processors processor generations ... with nearly two orders magnitude range in performance. 3083 finnally announced http://www-03.ibm.com/ibm/history/exhibits/mainframe/mainframe_PP3083.html above also has mention of preferred machine assist being supported. trivia ... 3083 involved removing one of the processors in 3081 in the frame. unfortunately, processor 0 was physically at the top of the box. there was concern that the simplest, straight-forward removal of processor 1 would make the box dangerously top-heavy. past posts in this thread: http://www.garlic.com/~lynn/2010d.html#58 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#59 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#60 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#61 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#62 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#63 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#66 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#69 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#70 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#71 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#72 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#73 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#78 LPARs: More or Less? -- 42yrs virtualization experience (since Jan68), online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
nominally there was a business case that customers then would naturally move much of their posix workload to MVS platform I had been told that one reason for Posix support in MVS was to allow bids for government contracts supercomputer would send hyperchannel message to the ibm mainframe, the ibm mainframe would locate the data (possibly staging to disk) and load dasd channel program into the hyperchannel device adapter That's exactly what Cray's Superlink product did. It used MVS as a data server, data manager, for the Cray. Bob Shannon Rocket Software -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. bshan...@rocketsoftware.com (Bob Shannon) writes: I had been told that one reason for Posix support in MVS was to allow bids for government contracts ... That's exactly what Cray's Superlink product did. It used MVS as a data server, data manager, for the Cray. re: http://www.garlic.com/~lynn/2010d.html#69 LPARs: More or Less? government was one of the biggest drivers towards commoditization ... including coining the term COTS (did some work in the past with the person that coined the term). The policy was to have posix all over the place ... as well as the applications using posix ... so that the applications could be trivially moved between platforms. The reality may not have always corresponded with the intention (sometimes it just turned into proforma checklist). Another (besides NCAR and Mesa Archival) was LANL system which was being marketed as Datatree by General Atomics. LLNL had their own system that ran directly on Cray ... and in ha/cmp project ... we were funding port of it to RS/6000 as part of commercial product Unitree. In the 80s, I would get sporadically get called into customers that were running hyperchannel connected to IBM mainframes. In 1980, STL was bursting at the seems and needed to move 300 people from the IMS group to offsite location. They had tested remote 3270s and found it totally unacceptable for their work. I got roped into writing HYPERChannel remote device support ... so that the 300 IMS people could have local (channel attached) 3270s back to their vm/cms interactive service (as well as remote channel attached tapes printers in their bldg). There was then attempt to allow the hyperchannel vendor to release my software ... which several organization in the company overruled. Then the hyperchannel vendor had to recreate much of my software from scratch (but local branch people would still frequently call me into their customers). for other IMS topic drift ... when Jim was leaving for tandem ... he was palming off several things ... including DBMS consulting to the IMS group ... old email refs: http://www.garlic.com/~lynn/2007.html#email801016 of course, for a period, it was also the federal govenment that was mandating OSI products (GOSIP) and that tcp/ip and the internet was going to be completely eliminated. Again that turned out to not quite correspond with reality. One of the things periodically pointed out was that the IETF required two interoperable implementations before things could progress in standards process ... while ISO didn't even require a passed standard to have demonstrated that it was even implementabled. For a while I was on the XTP technical advisory board (of course the communication group strongly objected to my being there) and help take HSP (high-speed protocol) to x3s3.3 (iso chartered body responsible for standards corresponding to OSI level 34). x3s3.3 refuseed the activity because it was under ISO mandates to only standardize things the conformed to OSI. HSP didn't conform to OSI because 1) it supported internetworking ... a layer that doesn't exist in OSI 2) it went directly from top of transport (layer 4) directly to LAN MAC interface (sits somewhere in the middle of networking, layer 3) bypassing OSI layer 3/4 interface 3) it went directly to LAN MAC interface ... LAN MAC interface doesn't exist in OSI misc. posts mentioning XTP /or HSP http://www.garlic.com/~lynn/subnetwork.html#xtphsp TCP/IP is the technology basis for the modern internet, NSFNET backbone was the operational basis for the modern internet, and CIX was the business basis for the modern internet. We had been working with NSF and various of the institutions for quite a while related to NSFNET backbone ... misc. past email http://www.garlic.com/~lynn/lhwemail.html#nsfnet with lots of internal objections. At one point the director of NSF wrote the corporation a letter copying the CEO and chief scientest trying to help us with our internal political problems. However that just worked to aggrevate the internal politics. misc. past posts on the subject http://www.garlic.com/~lynn/subnetwork.html#nsfnet Part of the reason for participation in NSFNET backbone ... was we already had a high-speed backbone running internally (one of NSF comments along the way was what we already had running was at least five years ahead of all BIDS to build NSFNET ... aka part of the internal politics was we were prevented from bidding on NSFNET). Misc. past posts mentioning my high-speed data transport project (HSDT) http://www.garlic.com/~lynn/subnetwork.html#hsdt Part of the reason that NSFNET RFP called for T1 links was that HSDT could demonstrate a lot of T1 (and higher speed) links already in operation. It turned out that the winning bid didn't actually install T1 links, they installed 440kbit links ... and then to sort of meet the letter
Re: LPARs: More or Less?
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. re: http://www.garlic.com/~lynn/2010d.html#69 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#71 LPARs: More or Less? for other folklore tidbit ... some old pictures ... including a shot of the login logo screen done for the 300 3270s channel attached terminal in offsite bldg for the IMS group: http://www.garlic.com/~lynn/lhwemail.html#oldpicts the IMS group was effectively seeing the same interactive response at the offsite bldg as they had with the channel attached 3270s in the bldg. an interesting side-effect was that moving the 3274 (channel-attached) controllers to the off-site building, the datacenter mainframe saw 10-15% system thrput improvement. The conventional wisdom at the time was to spread all the 3274 controllers across 15 channels shared with disks. However, the 3274 controllers had significant channel busy overhead per operation (independent of bytes transferred). Relocating the 3274 controllers to offsite building (connected to multiple hyperchannel A510 channel emulators) and replacing them with A220 host channel box (that had significantly faster circuits and enormously reduced channel busy for the same operations) resulted in the 10-15% overall system thruput improvement (eliminating the enormous 3274 channel busy interferance with disk i/o). misc. past posts mentioning HSDT activities http://www.garlic.com/~lynn/subnetwork.html#hsdt for other topic drift ... recent thread discussing the 3274 controller having worse human factors for interactive computing compared to earlier 3272 http://www.garlic.com/~lynn/2010d.html#41 Happy DEC-10 Day http://www.garlic.com/~lynn/2010d.html#44 Happy DEC-10 Day the first mainframe tcp/ip product had some issues ... including being quite cpu intensive ... burning a 3090 processor getting about 44kbytes/sec thruput. I added RFC1044 support to the product ... and in some testing at cray research (trip to cray, plane departed SFO 20 minutes late but managed to be wheels up minutes before the earthquake hit) got sustained mbyte/sec between cray and 4341 ... using only modest amount of the 4341 (about 500 times improvement in the bytes moved per instruction executed). misc. past posts mentioning doing rfc1044 support http://www.garlic.com/~lynn/subnetwork.html#1044 The TCP/IP product was also made available on MVS with an emulation for the vm370 diagnose feature (with equally poor processor overhead w/o the rfc1044 support). -- 42yrs virtualization experience (since Jan68), online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
George, I think your saying VM is the only true operating system will draw some flack. I've never heard before that a true operating system has to run other OS's underneath it. Also, what about z/OS's running of Unix. Isn't that kind of like running another operating system underneath it? Eric Bielefeld Sr. Systems Programmer IBM Global Services Division Dubuque, Iowa 414-477-7259 - Original Message - From: George Henke gahe...@gmail.com I have since come to realize that even though MVS is more robust with more functionality, that when all is said and done, VM is really the only true operating system, because it is the only operating system that can run other operating systems. In effect reducing MVS to the level of a CICS. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
George: Allow me to fill you in a bit on at least one of the MVS group's attempt to do in VM. IIRC, it was shortly after the death of FS (Future Systems) when I and several others were selected for a task force to answer the question how can we reduce the amount of development required to modify our operating systems (MVS and VM) to support any new processors that POK develops? We looked at several ways to make the nuclei of both systems similar and couldn't find an acceptable solution. One of the members of the task force, Karl Finkemeyer, had developed an idea he called the thin layer while at the Heidelburg Scientific Center (BTW, this eventually led to PR/SM). We argued that the main uses of VM were: 1) to support migration from one operating system to another and 2) support of the CMS development environment. We determined that the thin layer would support the migration issue, as it would provide enough independent system images (two or more) which would allow coexistence of different operating systems in the same CEC. We also believed that if we could effectively run CMS in MVS, that this would solve issue number 2 because it would support hundreds of CMS users. We believed that if we could do both, there would be no need for VM. At least one of the VM advocates immediately resigned from the task force at that time. Four of us teamed up to do a proof of concept by installing a running CMS under MVS. We added a CMS command to TSO which caused TSO to GETMAIN a sufficiently large area of storage from its own address space and then to load the CMS nucleus in that storage. Using SIE, it would dispatch the CMS nucleus. I implemented a CMS file system mini-disk structure in VSAM using control area access and later planned to use the VSAM actual block processor. Our proof of concept worked sufficiently well that the decision was made to staff the CMS under MVS project. Karl and I were to be the technical team leads of the two development teams. We were in the process of staffing when the project was killed. My understanding is that a devout VM advocate let the word slip at SHARE, which caused Gene Amdahl to declare publicly that he would support VM if IBM were to abandon it. Since we never used VM to support our project's development (except as a model for comparing our TSO/CMS version to VM's CMS), I can't agree that our use of VM was necessary to our project's development, and was not the reason the project was cancelled. Of course, we all know that PR/SM was eventually released and I have always held that CMS under MVS helped pave the way for OMVS, but that's only conjecture. Mike Myers Mentor Services Corporation On 2/19/2010 7:14 PM, George Henke wrote: l...@garlic.com wrote: The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computersas well. Wow, Lynn and Anne, thank you for that wonderful history. I remember it well I did not arrive on the scene at POK (bldg #10, I think, Global Services) until late, and then only as an outsider consultant (only a Class B integrator, not a Class A developer like yourself). But I remember the war stories I heard there, even then, of how the MVS group had tried to do in VM, until top management found out somehow that the MVS group was quietly using (needed) VM to test MVS. And I remember HONE, but I did not know it was driven by VM. I remember it as maybe a system to pose technical questions to. And then, of course, there was PROFS, IBM's own precursor to email. It had it all including an organization chart. Those were the days Thank you. On Fri, Feb 19, 2010 at 6:43 PM, Anne Lynn Wheelerl...@garlic.comwrote: The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. gahe...@gmail.com (George Henke) writes: After all is not MVS a far more robost operating system than VM which, by the admission of its own authors, is really little more than a hypervisor developed, of yore, to test different versions of MVS? some number of commercial online timesharing service bureaus were spun-off providing (secure) online interactive operation. recent mention of tymshare here http://www.garlic.com/~lynn/2010d.html#57 Adventure - Or Colossal Cave Adventure however, there were others. a couple of them relatively rapidly moved up the value chain providing all sorts of financial information (including to numerous highly competitive organizations on wallstreet in secure environment). misc. past posts mentioning commercial timesharing operation http://www.garlic.com/~lynn/submain.html#timeshare for much of its life vm/cms provided major interactive computing in addition to virtual guest testing. in the wake of the 23jun69 announcement, several internal HONE datacenters were setup with cp67 virtual machine to provide hands-on experience
Re: LPARs: More or Less?
George: Would my assertion that MVS could run another operating system (CS and UNIX) qualify it as a TRUE operating system by your definition? Mike Myers Mentor Services Corporation On 2/19/2010 8:10 PM, George Henke wrote: Absolutely fascinating Anne and Lynn. I was just a lowly COBOL applications programmer back in those days and finally taught myself BAL. I do remember the sad day of the unbundling and no more freebies. And then a few years later, I remember the day someone in the software group at Banker Trust, NY, showed me this new thing called, CP67, that could do what Run other operating systems? Impossible. Unheard of. We were all stunned. I have since come to realize that even though MVS is more robust with more functionality, that when all is said and done, VM is really the only true operating system, because it is the only operating system that can run other operating systems. In effect reducing MVS to the level of a CICS. How fascinating to see the evolution of software from VM/CMS to VAX/VMS and from GML to HTML. Absolutely amazing. You have a phenomenal background. You should write a book, the History of Data Processing, if you have not done so already. These things are too important not to survive the wreck of time. On Fri, Feb 19, 2010 at 7:46 PM, Anne Lynn Wheelerl...@garlic.comwrote: The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. gahe...@gmail.com (George Henke) writes: True. But it does not predate SVS, VS1, MVT, MFT, and OS Rel 17 from which (except for VS1) MVS evolved. Furthermore, a duck is still a duck no matter what you do to it, no matter how you dress it up. z/VM is certainly larger, more robust, and more powerful, than ever, but no matter what you do to it, it still just a hypervisor as one of the links included by some of the creators of PR/SM in the trail notes pointing out that PR/SM is now officially referred to as the LPAR Hypervisor. re: http://www.garlic.com/~lynn/2010d.html#58 LPARs: More or Less? http://www.garlic.com/~lynn/2010d.html#59 LPARs: More or Less? science center had original done virtual machine cp40 on a 360/40 with special hardware modifications to support virtual memory (they originally had tried for 360/50, but could get any because so many were going to FAA for ATC system). When standard 360/67 with virtual memory hardware support came available, cp40 morphed into cp67. past posts mentioning science center http://www.garlic.com/~lynn/subtopic.html#545tech a more detailed early history can also be found here: http://www.princeton.edu/~melinda lots of customers that had been sold 360/67s to use with tss/360 ... switched to cp67 when tss/360 had delivery problems (others just dropped back to running the machines in 360/65 mode with os/360). old post that has part of presentation I made at 68 SHARE meeting in Boston about lots of performance enhancements I had done for MFT (completely reworked stage2 sysgen for careful placement of datasets and PDS members for optimal disk arm mition) and cp67 (lots of code changes to significantly reduce cp67 pathlength) http://www.garlic.com/~lynn/94.html#18 CP/67 OS MFT14 One of the things that CP67 needed to handle for virtual machine operation was channel program translation ... creating a shadow copy of the virtual machine channel program ... with real addresses (rather than virtual machine addresses). SVS faced the same exact problem in EXCP processing handling the passed channel program. The SVS initial implementation started out by borrowing the channel program translation routine (CCWTRAN) from cp67 (basically MVT laid out in large virtual address space, with minimum support for single virtual address space, most of the work was CCWTRANS doing channel program translation for EXCP). One of the first distributed development projects was between Endicott and the science center to implement vm370 virtual machines in cp67 running on real 360/67. Part of this resulted in also creation of the cms multi-level source management infrastructure. The science center cp67 service had a lot of non-employees from various higher educational institutions in the boston area. As a result, there had to be a lot of procedures to keep 370 virtual memory activity from unauthorized people. The cp67 system running on the real 360/67 was cp67l, cp67h ran in a 360/67 virtual machine (away from prying eyes of unauthorized people) with the changes to simulate 370 hardware, cp67i ran in 370 virtual machine (with changes to conform to 370 rather than 360 virtual memory). This environment was running standard for a year before the first 370 with real hardware virtual machine was available. Then for a long time cp67i was standard operating system that ran internally on large number of 370s for long period (before vm370 was available). It took quite some time for science center got a real 370
Re: LPARs: More or Less?
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. m...@mentor-services.com (Mike Myers) writes: Allow me to fill you in a bit on at least one of the MVS group's attempt to do in VM. IIRC, it was shortly after the death of FS (Future Systems) when I and several others were selected for a task force to answer the question how can we reduce the amount of development required to modify our operating systems (MVS and VM) to support any new processors that POK develops? We looked at several ways to make the nuclei of both systems similar and couldn't find an acceptable solution. One of the members of the task force, Karl Finkemeyer, had developed an idea he called the thin layer while at the Heidelburg Scientific Center (BTW, this eventually led to PR/SM). We argued that the main uses of VM were: 1) to support migration from one operating system to another and 2) support of the CMS development environment. We determined that the thin layer would support the migration issue, as it would provide enough independent system images (two or more) which would allow coexistence of different operating systems in the same CEC. We also believed that if we could effectively run CMS in MVS, that this would solve issue number 2 because it would support hundreds of CMS users. We believed that if we could do both, there would be no need for VM. At least one of the VM advocates immediately resigned from the task force at that time. Four of us teamed up to do a proof of concept by installing a running CMS under MVS. We added a CMS command to TSO which caused TSO to GETMAIN a sufficiently large area of storage from its own address space and then to load the CMS nucleus in that storage. Using SIE, it would dispatch the CMS nucleus. I implemented a CMS file system mini-disk structure in VSAM using control area access and later planned to use the VSAM actual block processor. Our proof of concept worked sufficiently well that the decision was made to staff the CMS under MVS project. Karl and I were to be the technical team leads of the two development teams. We were in the process of staffing when the project was killed. My understanding is that a devout VM advocate let the word slip at SHARE, which caused Gene Amdahl to declare publicly that he would support VM if IBM were to abandon it. Since we never used VM to support our project's development (except as a model for comparing our TSO/CMS version to VM's CMS), I can't agree that our use of VM was necessary to our project's development, and was not the reason the project was cancelled. Of course, we all know that PR/SM was eventually released and I have always held that CMS under MVS helped pave the way for OMVS, but that's only conjecture. the decisionto shutdown the (vm370 development group) burlington mall location was being kept secret until the last minute ... supposedly to minimize the possibility that any of the group could find alternatives before being moved to POK. It leaked in the bldg. (had previously been occupied by SBC before service bureau corporation was given to CDC) ... a couple months early and then there was a witch hunt to find out who leaked the information (between the closing hanging over their heads and the witch hunt to find who leaked the information ... those last few months weren't very pleasant place). One of the unfortunate things ... was somebody in the group had done a significant enhancement for O/S simulation (including all kinds of stuff for generalized OS disks). The base CMS code for O/S simulation was under 64kbytes (there was some joke about CMS 64kbytes O/S simulation being a significant better price/performance than the humongous bloated MVS O/S simulation). As part of killing vm370/cms ... and the person responsible not moving to POK (but leaving the company) all of that got lost. In the early 80s, I ran a corporate advanced technology symposium (the first that had been held for several years ... all sorts of things went by the wayside in the aftermath of FS failure) ... one of the talks was about running CMS applications under MVS. old reference http://www.garlic.com/~lynn/96.html#4a John Harmann's Birthday Party However, one of the issues with CMS wide-spread sucess for interactive computer ... was some amount of human factors consideration. Just being able to run CMS applications didn't help/improve MVS (or TSO) human factors. A trivial example is the enormous degradation of (VTOC PDS member) multi-track search on response. For a period, research/bldg28 had 370/168 running MVS and 370/158 running vm370 ... with a dasd farm that was connected to all processors. However, there were strict rules that certain controllers were dedicated for vm/cms and certain controllers were dedicated for mvs. One day, an operator accidentially mounted a 3330 MVS pack on a vm/cms string ... and within five minutes the
Re: LPARs: More or Less?
W dniu 2010-02-20 00:05, George Henke pisze: [...] Unless you want an administrative nightmare or have an army of system programmers, you will follow IBM's strong recommendation to share everything as much as possible: SHARED PARMLIB, SHARED MASTERCAT, SHARED PROCLIB, SHARED JESPOOL. In fact that means sysplex (MAS require base sysplex). So, for performance reasons you should follow another IBM recommendation: parallel sysplex. And another one: single RACF db. In fact you get multi-member sysplex (SYSTEM!) which is used for production, development, QA, stress tests... I'm not IBM, b ut I wouldn't recommend it, no way. g BTW: Unless you have poor administrators, there is no nightmare in administration of non-shared PARMLIBs, MASTERCATs, PROCLIBs, etc. etc. The overhead for repeated activities can be reasonably small. In simple words: you think once, code once, check once, test once, and finally implement several times - usually by issuing multiple SUBmits. My €0.02 -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237 NIP: 526-021-50-88 Wedug stanu na dzie 01.01.2009 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 118.763.528 zotych. W zwizku z realizacj warunkowego podwyszenia kapitau zakadowego, na podstawie uchway XXI WZ z dnia 16 marca 2008r., oraz uchway XVI NWZ z dnia 27 padziernika 2008r., moe ulec podwyszeniu do kwoty 123.763.528 z. Akcje w podwyszonym kapitale zakadowym BRE Banku SA bd w caoci opacone. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. m...@mentor-services.com (Mike Myers) writes: Of course, we all know that PR/SM was eventually released and I have always held that CMS under MVS helped pave the way for OMVS, but that's only conjecture. re: http://www.garlic.com/~lynn/2010d.html#66 LPARs: More or Less? oh ... we did some amount of consulting to the executive pushing posix support into MVS ... nominally there was a business case that customers then would naturally move much of their posix workload to MVS platform. the issue in the early 80s was that there was a sharp decrease in the cost of building a computer platform ... lots of mini-computer workstation vendors springing up all over the place based on some chip or another. the problem was that the proprietary operating system paradigm from the 60s 70s ... didn't see a corresponding drop in costs. To some extent these vendors were being forced into something like a portable unix ... because of the drastically reduced costs to get it up, running, and shipped on their hardware platform. customers the market then started getting caught up in this ... because it started to provide them with independence from proprietary hardware ... a software layer that supposedly offered relative portability across a wide-range of increasingly commoditised hardware platforms. This was large part of motivation behind POSIX standards activity ... further providing the market with hardware independence (and being able to easily switch to the most cost effective hardware platform). Few of the people associated with the MVS posix support understood the market drivers behind posix. as an aside, the executive responsible for the original MVS posix support ... was also out doing various and sundry other kinds of activity. One involved NCAR and Mesa Archival. NCAR had hierarchical storage system (early NAS/SAN) with 370 mainframe as controller and CKD dasd farm all interconnected with HYPERChannel to various supercomputers. supercomputer would send hyperchannel message to the ibm mainframe, the ibm mainframe would locate the data (possibly staging to disk) and load dasd channel program into the hyperchannel device adapter ... and return the channel program handle to the supercomputer. the supercomputer would then directly invoke the channel program (ibm mainframe being used for control but not for actual data flow). For a period, NCAR attempted to spin this off as a product in an independent company Mesa Archival ... with lots of funding by the executive also doing MVS posix support (and we were used to periodically review/audit how they were doing; part of it was migrating the ibm mainframe code to rs/6000 and replacing all the CKD disks with FBA disks). similar hyperchannel approach was done by some number of other institutions. in the standards groups for IPI disks and HIPPI channels ... part of the standard activity was HIPPI switch support for 3rd party transfers (allowing the hyperchannel nas/san disk farm implementation to be mapped to IPIHIPPI environment; aka controller setting up the transfer mechanics but actually occuring from/to a different processor). HIPPI was standardization of 100mbyte/sec cray channel ... being championed by LANL. The 3090 group tried to play in 100mbyte/sec HIPPI (disk arrays, high-speed graphics, misc. other stuff) ... but the 3090 channel interface was nowhere near fast enough. The only thing that came close was the extended store bus ... so there was this interesting thing done with HIPPI interface being cut into the side of the extended store bus. Then because the only operations to extended store were synchronous 4k byte moves, I/O programming for HIPPI channel became sort of analogy to PEEK/POKE operations (found in the PC world) using synchronous 4k byte extended store move operations (to reserved extended store addresses). -- 42yrs virtualization experience (since Jan68), online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well. m...@mentor-services.com (Mike Myers) writes: Four of us teamed up to do a proof of concept by installing a running CMS under MVS. We added a CMS command to TSO which caused TSO to GETMAIN a sufficiently large area of storage from its own address space and then to load the CMS nucleus in that storage. Using SIE, it would dispatch the CMS nucleus. I implemented a CMS file system mini-disk structure in VSAM using control area access and later planned to use the VSAM actual block processor. I had earlier done a paged mapped filesystem for CMS on cp67 and then migrated to vm370 http://www.garlic.com/~lynn/2006v.html#email731212 http://www.garlic.com/~lynn/2006w.html#email750102 http://www.garlic.com/~lynn/2006w.html#email750430 and shipped internally to the csc/vm (and later sjr/vm) internal customer sites. misc. past posts mentioning paged mapped file system http://www.garlic.com/~lynn/submain.html#mmap I also had done all sorts of fancy stuff with shared segments ... somewhat akin to tss/360 (or FS ... one of my less than complimentary comments about FS was that I had stuff already running that was better than what they were trying to do). However, a large part of CMS used os/360 conventions, assemblers compilers which gave me lots of problems with some of the fancier features. misc past posts with discussions of some of those problems http://www.garlic.com/~lynn/submain.html#adcon the original intention was to use some of the fancier parts of the 370 virtual memory architecture. However, when 360/165 ran into schedule problems retrofitted virtual memory hardware to the 165 and the favorite son operating system in POK said they could see no reason for the fancier features ... they were droppes (as part of 165 picking up six months in schedule and allowing 370 virtual memory annoncement not to be delayed). The standard vm370 product was also going to make a little use of some of the new features ... but when they were dropped from the hardware product ... vm370 had to go back and do some ugly hacks to compensate. except for short time for pc/370 (xt/370, at/370) the page mapped stuff was never shipped outside the corporation ... even tho i can demonstrate extremely significant disk thruput and pathlenght improvements. I had some number of benchmarks showing identical applications running on identical 3380s ... ran three times faster with CMS paged mapped filesystem than with standard CMS filesystem. -- 42yrs virtualization experience (since Jan68), online at home since Mar1970 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
When one attempts to define what constitutes an Operating System, most definitions tend to center around the fact than an OS manages various hardware resources (CPU, memory, I/O paths, I/O devices) and provides various logical resources and functions useful for running applications. Perhaps a more generic way of viewing a typical Operating System is that it creates the illusion of a virtual machine that is better suited as an application platform - an environment in which many of the complexities of dealing with I/O, resource sharing, security, integrity, etc. at the actual hardware level are are resolved by the Operating System and hidden from and can be largely taken for granted by application programmers. VM is usually regarded as a control program rather than an Operating System precisely because it passes on to the the virtual machines running under it all the complexity of the actual hardware, including access to and the risks associated with privileged instructions. While VM does make some enhancements available to the virtual machines, primarily to support the CMS environment in a virtual machine and to provide controls for the virtual machines themselves; a generic Operating System running under VM uses very little beyond the host hardware instructions. VM is cool and can be a very useful tool, but trying to implement a complex multi-user application with shared data using bare VM virtual machines with just the functions provided by VM shows why many would hesitate to classify it along with other Operating Systems, much less consider it the only true operating system. On 02/19/2010 07:10 PM, George Henke wrote: ... I have since come to realize that even though MVS is more robust with more functionality, that when all is said and done, VM is really the only true operating system, because it is the only operating system that can run other operating systems. In effect reducing MVS to the level of a CICS. ... -- Joel C. Ewing, Fort Smith, ARjremoveccapsew...@acm.org -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Let's face it, even by IBM's admission, PR/SM is little more than VM in microcode. So why put VM in microcode in the first place and limit us to only 60 LPARs. Why not just give us VM as is and let us decide how many instances of z/OS under z/VM we would like to run as well as the mix with z/LINUX, AIX, etc? And then lock us in to this configuration with sub-capacity pricing. Maybe because it will sell more hardware? How many LPARs does it take to screw in a light bulb?, to paraphrase the old sysprog question. None, it is a hardware problem. Don't fence me in As Ken pointed out earlier in this trail, it is indeed possible to put it all in one LPAR and configure WLM, in lieu of PR/SM, to manage the weightings. Thank you, Ken, great hearing from you again. We are a small shop here and my client is looking at $6 million in additional software charges just to add a new QA LPAR and, quite frankly, if it were my money, for that price, I would find some way to run QA in the DEV LPAR. Hijacking the DR LPAR, however tempting, will not save anything either because the incremental software costs are not incurred until there is a real disaster. Centralize whatever and you minimize cost (TCO) and maximize control, albeit at the cost of flexibility; Management 101. After all is not MVS a far more robost operating system than VM which, by the admission of its own authors, is really little more than a hypervisor developed, of yore, to test different versions of MVS? Why would we NOT use MVS instead of VM, alias PR/SM, to do multitasking and manage workloads? Why look to a hypervisor to do the job that MVS was designed to do and far more capable of doing? Just because it is nice and neat, has the appearance of being separated, and is someone else's money? Someday management will grant bonuses to sysprogs for a percentage of the $ they will save the company by finding more cost-efficient ways of attaining their goals. Actually, Pratt and Whitney, already does this. As for SOX and customer demands for their own LPARs, there needs to be a risk assessment first. Where's the risk? Controls are designed for risk. No risk, no need for a control. Playing up risk is one of the oldest tricks in the saleman's book.. I can almost hear Robert Preston now . . . O, There's trouble, trouble, I say, right here, in River City. On Wed, Feb 17, 2010 at 4:17 PM, Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net shmuel%2bibm-m...@patriot.net wrote: In b53f38421002170726k4585f228k9c4048891605b...@mail.gmail.com, on 02/17/2010 at 10:26 AM, George Henke gahe...@gmail.com said: Here is what I thought was a dumb question until someone posed it to me yesterday. Why have a separate QA LPAR and not just leave QA in the DEV LPAR? Do you freeze DEV when doing QA on a new release of the operating system? If not, then you need both. Can't MVS (z/OS) handle it? Handle what? Multiple release and service levels? Separation of DASD? Why replicate the z/OS operating system a gazillion times when z/OS already has everything needed. Needed for what? I know single point of failure at all that jazz, but then what do we have a DR box for anyway? Hint; what does the D stand for? If it were really my money I was playing with, would I have sooo many LPARs just for neatness or so-called integrity, control, apple pie, and motherhood? That's a question that only you can answer. It's not my dog. But that cannot be achieved with a single instance of z/OS, a software sandbox, and a DR box? If you never install service or upgrade. Don't we already logically separate DEV, TEST, UAT, and PROD in separate CICSes, DB2s, etc. To some extent. These are hard questions like, Is the emperor really wearing anything?. No, they are loaded questions like Have you stopped beating your wife? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- George Henke (C) 845 401 5614 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
So why put VM in microcode in the first place and limit us to only 60 LPARs. Less overhead. I've not seen a need for 'only 60 LPARs', yet. But, I'm sure somebody out there has/will have it. Why not just give us VM as is and let us decide how many instances of z/OS under z/VM we would like to run as well as the mix with z/LINUX, AIX, etc? Two reasons: 1. Complexity -- you need z/VM skills and z/OS skills. I've only known one sysprog with both at sufficient skill levels to be able to manage both effectively. 2. Why should IBM 'give' us anything? Last I heard they're still responsible/accountable to their shareholders. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
Why PR/SM over VM - less overhead, less software to manage/understand Is anyone running close to 60 z/OS LPARs on a single box? If you really need it you can run VM if you want to. Why $6 Million to add an LPAR? Are you adding capacity or using more of what you already have? Have LPAR/instance based software contracts? Regulatory/contractual requirements have little to do with efficient use of resources. If I was a paying customer on someone else's box I would want my own LPAR, DASD, Network separate from other customers (possibly competitors). It might be unlikely but I could write authorized code to snoop into your data or you mine. -Original Message- George Henke Let's face it, even by IBM's admission, PR/SM is little more than VM in microcode. So why put VM in microcode in the first place and limit us to only 60 LPARs. Why not just give us VM as is and let us decide how many instances of z/OS under z/VM we would like to run as well as the mix with z/LINUX, AIX, etc? And then lock us in to this configuration with sub-capacity pricing. Maybe because it will sell more hardware? How many LPARs does it take to screw in a light bulb?, to paraphrase the old sysprog question. None, it is a hardware problem. Don't fence me in As Ken pointed out earlier in this trail, it is indeed possible to put it all in one LPAR and configure WLM, in lieu of PR/SM, to manage the weightings. Thank you, Ken, great hearing from you again. We are a small shop here and my client is looking at $6 million in additional software charges just to add a new QA LPAR and, quite frankly, if it were my money, for that price, I would find some way to run QA in the DEV LPAR. Hijacking the DR LPAR, however tempting, will not save anything either because the incremental software costs are not incurred until there is a real disaster. Centralize whatever and you minimize cost (TCO) and maximize control, albeit at the cost of flexibility; Management 101. After all is not MVS a far more robost operating system than VM which, by the admission of its own authors, is really little more than a hypervisor developed, of yore, to test different versions of MVS? Why would we NOT use MVS instead of VM, alias PR/SM, to do multitasking and manage workloads? Why look to a hypervisor to do the job that MVS was designed to do and far more capable of doing? Just because it is nice and neat, has the appearance of being separated, and is someone else's money? Someday management will grant bonuses to sysprogs for a percentage of the $ they will save the company by finding more cost-efficient ways of attaining their goals. Actually, Pratt and Whitney, already does this. As for SOX and customer demands for their own LPARs, there needs to be a risk assessment first. Where's the risk? Controls are designed for risk. No risk, no need for a control. Playing up risk is one of the oldest tricks in the saleman's book.. I can almost hear Robert Preston now . . . O, There's trouble, trouble, I say, right here, in River City. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
-Original Message- From: IBM Mainframe Discussion List On Behalf Of George Henke [ snip ] Someday management will grant bonuses to sysprogs for a percentage of the $ they will save the company by finding more cost-efficient ways of attaining their goals. I think that day has come and gone. Actually, Pratt and Whitney, already does this. For every rule there is at least one exception. But which is the rule, and which the exception? -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: LPARs: More or Less?
On Fri, 19 Feb 2010 11:41:07 -0500, George Henke wrote: Let's face it, even by IBM's admission, PR/SM is little more than VM in microcode. The implementation of PR/SM is indeed similar to VM. It may even share quite a bit of code, but it is not virtual. You have to allocate the processor storage to each LPAR. Real devices have to be provided for each of them. Consoles, for example. So why put VM in microcode in the first place PR/SM was implemented because Amdahl had MDF and their customers liked it. and limit us to only 60 LPARs. That is a lot of LPARS when you consider that you have to allocate storage to each of them. How much memory do you have, and how many ways are you willing to divide it? -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html