>As you mentioned,it is important that the work that newly arrives into the >system is properly classified and has not overly aggressive goals. However, >it is equally important that the other "important" is correctly classified >with a goal that is aggressive enough to protect against other work. This last >item is "usually" what contributes most to such unwanted effects.
WLM makes it settings based on historical events, right? So, the service class that OMVS work is assigned to might currently have a higher dispatching priority when that bunch of jobs is submitted. It will take WLM a few policy adjustment cycles to correct that. Also, if many such jobs are submitted in parallel, WLM might have to start batch initiators for the jobs, and then at least two BPXAS initiators per job for the UNIX processes for at least a couple of jobs. Then, depending on how quick the UNIX work terminates, BPXAS inits may be reused for the other job's UNIX processes. I assume there is more UNIXish work being done under the ssh process, so another bunch of BPXAS may be required. You might want the customer to have a look at the operlog and find out if there is a spike of INIT / BPXAS being started. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
