On Fri, 6 Oct 2017 18:22:34 +0800, Tommy Tsui wrote: > We are running in wlm mode with schedule environment, wlm managed all >class with xeqcount=200, but we don't know why when all new jobs reached >around 20, and CPU reached 100% all other new coming job will be in "job >await main select" status, we don't know why, is it CPU reached 100%, and >wlm decided not to start more initiator?
WLM manages the number of initiators based upon resources available and the goals that you have set. If your goals are too aggressive and are not being met, WLM is less likely to start more initiators. CPU at 100% suggests to me that the system can't productively do more work. What do you hope to accomplish by having more jobs running? If you are using all the available CPU resources and you start twice as many similar jobs, they will likely all run twice as long. Perhaps longer because of additional work required to manage the additional jobs, and possible shortage of other resources, such as memory. >Can we force to start new jobs? In JES2, you can issue $S JOB and WLM will start another initiator for that job. Your message suggests to me that you are JES3. I don't know if JES3 has a similar function. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
