WLM considers all LPARs within the sysplex to be equal. WLM by itself, has no control over where the work is initiated.
In conjunction with JES2 at the z/OS 2.4 level and higher, the ability was created to allow work to be started via "workload managed initiators". Without going into the details, job queue time is now included as part of the WLM performance index when deciding whether to add work to the system. Also with WLM managed initiators, the current PI for the work on a given LPAR Is taken into consideration when deciding where to initiate the work (subject to other considerations(scheduling environment, system affinity,.....) ). This can also be complicated by a multiple JESPLEX with a SYSPLEX. The short story on Workload Managed initiators is as follows: 1) JES2 and WLM initiators can be mixed "at will". Each jobclass defined/used should be either JES or WLM managed, but not both. i.e. a given jobclass is either workload managed or jes managed. 2) A separate WLM service class should be defined for the WLM managed work to prevent misleading PI's based on the queue time component of the WLM PI calculation. There is a lot more to this, and I suggest reading the JES2 and WLM manuals extensively before proceeding. There are also several presentations from SHARE,.... that are quite helpful. HTH, <snip> WLM takes the load and performance of LPARs in consideration, by starting and stopping WLM Managed Initiators on systems that have capacity available or are overloaded. But it does this very coarse, putting a line at 95% utilization. When you have several LPARs that are running near 100%, some of which are overloaded with a bad PI and others still can take more load, WLM considers them all the same. I am looking too at a mechanism to manage WLM managed batch on this type of LPARs. I think the way I go is by allowing or withholding certain jobclasses from certain systems with the $tjobclass(a,b,c,d),QAFF=-name and QAFF=+name. I do this now manually every now and then when I see an overloaded system, but I am still looking for an interface to the information you mention (PI, capping) to automate this. it is really a miss, that WLM does not do this more detailed. Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Munif Sadek Sent: Wednesday, July 24, 2013 07:02 To: IBM-MAIN@LISTSERV.UA.EDU Subject: WLM managed workload Dear Listers Can some one please point me in the right direction to implement WLM managed job class that can schedule jobs on different LPARS selected on basis of service class Performance Index and/or soft CAPPING status of individual LPAR. Creating Scheduling Resources / Environment and using automation to turn off/on resources is a possibility but I prefer the first option.. By the way it is DB2 9.0, z/OS 1.12 parallel sysplex environment. </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
