Sent from my iPhone On Dec 17, 2014, at 12:38 PM, Lizette Koehler <[email protected]> wrote:
> How is the dasd handled? Is it separate between Prd and other LPARs? Or do > you share your dasd. Dasd is shared. > > In other words any LPAR can see any dasd for any other LPAR or is it PRD > dasd is only on prd and not accessible by the other LPARS? Its all shared. > How does Operation identify the issue? Are they looking at an alert? Or a > Monitor (Tivoli Omegamon, other?) That's one of the outstanding questions. > How is the network during this time? Is connectivity optimal or slowed > down? Operations is adept at monitoring. They do not identify any network issues. I'll ask them specifically next time. > > Lizette > > >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:[email protected]] On >> Behalf Of L Hagedorn >> Sent: Wednesday, December 17, 2014 9:09 AM >> To: [email protected] >> Subject: Re: MIPS, CEC, LPARs, PRISM, WLM >> >> MVS Sysprogs reported the situation saying DB2DIST on LPAR A was affecting >> LPAR B. I didn't ask them for doc, but will next time. >> >> This is a runtime issue, unrelated to reported changes. That being said, > I'm aware >> WLM is changed frequently and without broadcast notification. >> >> This appears from time to time. I am new here (couple of months) so > cannot >> determine how long its been happening - could be months, could be years. >> >> I need to understand the interworkings of prism, WLM, and the LPARs, and > from the >> postings today, more about soft and hard capping. >> >> All input is appreciated. I have a learning curve in this area, so > telling me to look for >> something in RMF is welcome, along with any display commands where I can > see >> the caps. I have Mainview. >> >> Sent from my iPhone >> >> On Dec 17, 2014, at 8:35 AM, Lizette Koehler <[email protected]> >> wrote: >> >>> I would ask first, how do you know it is affecting the Prod LPAR. >>> >>> What evidence, RMF Reports, Performance monitors, etc. ? >>> >>> There should be, I think, so data that could explicitly show that is >>> what is happening. >>> >>> Is it all the time, some of the time? Is it a specific time when the >>> prod LPAR is affected? How long has it been going on? Is there a >>> point in time when this started? If so, what changes occurred at that > point? >>> >>> Lizette >>> >>> >>>> -----Original Message----- >>>> From: IBM Mainframe Discussion List [mailto:[email protected]] >>>> On Behalf Of L Hagedorn >>>> Sent: Wednesday, December 17, 2014 5:44 AM >>>> To: [email protected] >>>> Subject: MIPS, CEC, LPARs, PRISM, WLM >>>> >>>> Hi IBM-MAIN, >>>> >>>> We have a situation with multiple LPARS on a CEC, running DB2 asids >>>> prod, >>> test, >>>> dev. >>>> >>>> It is claimed a runaway DB2 DIST asid on the DVLP LPAR is burning CPU >>>> and stealing MIPS from the PROD LPAR and affecting production. >>>> >>>> Others claim this is not possible due to Prism. >>>> >>>> Will someone provide an overview of how Prism influences or controls >>>> MIPS >>> usage >>>> (CPU) across LPARs sharing the same CEC, what are the limiting or >>> controlling >>>> factors (if any), and how can the behavior be measured or reported >>>> upon so >>> I can >>>> explain this with supporting doc? Does WLM play a part in sharing CPU >>> across >>>> LPARs? >>>> >>>> Any information or referrals to doc is appreciated. >>>> >>>> Thanks, Linda > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
