My experience is that CICS will suffer if the LPAR is being soft capped, no matter what you try to do to this situation.
So I think the best and only solution is to avoid that the LPAR becomes capped by keeping the batch consumption under control. Not with a limited number of initiators, because which will not control CPU consumption, but with a Resource Group, which will keep the batch CPU consumption within the limits that would otherwise have caused capping. Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Tracy Adams Sent: 28 April, 2016 20:22 To: [email protected] Subject: WLM issue with a proposed solution So here is my issue: We have a soft capped LPAR that runs our DB2 and CICS regions and during the day some "marketing batch". On Wednesdays, the marketing batch (online submit via CICS) increases and by afternoon we hit our 4 hour soft cap. Once or twice while we are capped, the busiest CICS slow down to the point where some old automation kicks in to kill transactions over 45 seconds old, some of these transactions dump through DumpMaster, we then go to max sockets and more transactions dump and in 10 - 30 seconds all is fine again. What I see: The CICS regions have a DP around EC and are meeting their service goal of 99% under .5 seconds. But there are tens of thousands transactions that have led to this. The batch jobs (3-5 of them), while running 10 - 15 % cpu have a DP of C0 and are in a discretionary level of the service class. I believe the problem lies with the DB2 service class. That has a definition of velocity at 66 and it tends to run below that when there is more contention in the system. The DP of the DB2 region is F6. My theory: when this brown out occurs the resources are maxed out and the CICS regions being the ones that have meet their goal and will have to suffer many transactions missing the service goal to make the DP go up. They get hung up just long enough to cause the delays that trigger the "panic" automation to clear the stalled transactions. Chaos breaks out! My proposal: A. limit the batch jobs to a max of three by controlling open initiators for their job class. B. change the DB2 velocity to 60 C. Starve the CICS service goal by reducing it to 99% in .4 forcing his DP to be a little more desperate. Thoughts? TIA, Tracy ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
