Linda This may just be as simple as the Prod LPAR normally uses more than its defined weight and Ops/Users have become used to that level of throughput. When the Dev LPAR starts using more CPU and the box goes to 100% busy the weights are enforced. This may drive the Prod LPAR to a smaller share of the box than normal, and you get complaints.
Jerry Whitteridge Lead Systems Programmer Safeway Inc. 925 738 9443 Corporate Tieline - 89443 If you feel in control you just aren't going fast enough. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of L Hagedorn Sent: Wednesday, December 17, 2014 4:44 AM To: IBM-MAIN@LISTSERV.UA.EDU 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN "Email Firewall" made the following annotations. ------------------------------------------------------------------------------ Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ============================================================================== ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
