"Mark Zelden" <[email protected]> wrote in message news:<[email protected]>... > On Tue, 1 May 2012 21:39:05 +1000, Andrew Rowley <[email protected]> wrote: > > >Hi, > > > >I have read a few articles that say that multiple periods are not > >recommended for batch service classes. Multiple periods seems to be > >considered a bit old fashioned. > > > >I haven't been able to find anything clearly explaining why. I have > >always felt that they worked well. My best guess is that it is something > >to do with the behaviour of WLM managed initiators but I'm not sure. > > > >Can anyone shed any light, or point me to some further reading? > > > > I have never had much use for them. I only used them prior to goal > mode for a quick turn around / "express" JOBCLASS that maybe had > a 10 second CPU time limit. The idea was that if someone submitted > a job to that class that was a quick IEBGENER or compile they would > get in and out of the system quicker - even when the system was > busy. That doesn't really work well with goal mode, since DP > isn't "hard coded" like I had it on IEAIPSxx when I did such things. > Sure, you could assign that jobclass to a service class who's first period > had a high importance and CPU critical - but it's batch!
In Goal mode you specify the performance with Vel/Resp + Imp, the same as you did with DP prior to Goal mode. I use this to give relatively short jobs a better performance (Vel + Imp) in Period 1 than the longer running jobs falling into Period 2. Like your IEBGENERs. Remark to Allan's note 'batch is batch': it looks not that important to you. For us it is: several bussiness applications run in batch, with non-neglectable performance requirements. Kees. ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
