Here is the original document.... ftp://public.dhe.ibm.com/s390/zos/wlm/WLMinits.pdf
short version: Additional WLM managed initiators will be started when JES queue time becomes a significant component of the delay samples. (note: Held/duplicate jobs are not considered delayed). After some period of idle time, WLM managed initiators will be drained. The velocity and PI calculations are modified to include queue delay samples. The design is to lag somewhat behind in starting additional initiators, and delay their shutdown. Having run with them for a number of years, given proper goals, they will smooth out workload spikes. Job queueing is changed from priority with jobclass to FIFO across all WLM managed job classes. Initiators can be dynamically changed from JES managed to WLM managed via $TJOBCLASS,MODE=(WLM/JES). Warning: If running mixed JES/WLM inits, ensure you WLM classification rules to not comingle service classes between JES and WLM managed jobs. HTH, <sniP> This is about WLM managed initiator management. In "System Programmer's Guide to: Workload Manager", I read that independent of the goals set, WLM might start additional initiators if jobs are waiting in the input queue. WLM will consider "available CPU and memory" in its decision if and on which system to start more initiators. I wonder what the "available CPU" is when the system is running on a CEC with lots of white space. The system is allowed to use that capacity as long as the defined capacity is not exceeded in the four hour average. What does WLM look at? The defined capacity of the LPAR? The LPAR's share based on its weight? The number of CPs (LCPs)? What else? I'm trying to understand how our LPAR setup on the CEC is influencing WLM's preception of available CPU capacity and with this, its decision on how many initiators to start on a partition. </snip> -- Peter Hunkeler ---------------------------------------------------------------------- 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
