On Tue, 1 May 2012 22:06:55 +0200, Vernooij, CP - SPLXM wrote: >In our case, production batch varies from seconds to hours
That was my case too. It was several years ago that I was in a shop where I had primary responsibility for performance, but what I found there is that: During the day, most of the production jobs were shorter duration, with the longest running jobs being run at night There was very little non-production work at night During the day, CICS was the most critical and there was a lot of development batch and TSO work Even at night, about as many jobs were of short duration as long duration jobs. At night, there was little competition for resources. For my shop I set a goal for production of 50% complete in 30 minutes. I did that after some analysis of the production jobs that run over a period of time and found that about half of the production jobs run in under 30 minutes. By using a percentile goal like this, WLM gave priority to production over non-production. This works because WLM manages the service class, not individual jobs. For example, when WLM changes the dispatching priority of a service class, every job in the service class is set to the same DP. As long as the arrival rate of shorter work is high enough, the longer running jobs go along for the ride. Most non-production batch was in discretionary. I was using WLM managed initiators for almost everything, which helped the performance of everything because it kept the system from being over-initiated. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
