On 21/03/2025 12:11 am, Jousma, David wrote:
We have a fairly large development environment that no matter how much capacity we would give it, its never enough. One thing that makes the problem worse, is that a single user submits multiple jobs with unique jobnames taking available inits from others. I know we could limit them to a specific jobname, forcing them to single thread jobs, but I’d rather do something in job selection that is jobname agnostic, but limits a single user to some number of concurrent jobs by userid? Looks like JES exit 14 or likely 49 could be utilized?
Maybe opening things up and controlling with WLM would actually make things better?
I have had success in the past by setting up a service class with 2 periods. First period is e.g. 80% complete in 1 minute, second period is discretionary.
Then open up the initiators so jobs aren't queueing before execution, or allow WLM to manage initiators to achieve the 1st period goal. MTTW dispatching in discretionary manages the contention between jobs.
The biggest caveat with discretionary is that you MUST have a large enough percentage of work running in discretionary that the system isn't monopolized by non discretionary work. Having small amounts of discretionary work doesn't work. Large amounts of discretionary works beautifully.
-- Andrew Rowley Black Hill Software ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
