Thats right, it has to do with software billing. A loop in batch causes high MSU and might create a high 4 hr rolling average if batch and online falls partial in 4HRA and that might hurt online work.(software capping)
2009/4/6 Ron Hawkins <[email protected]> > Dick, > > I'm confused about your objectives. How will online work suffer from a four > hour rolling average in batch? The rolling average has a lot to do with > software billing and very little to do with performance. > > Do you want to restrict the available capacity of the LPAR during the batch > run to something less than the capacity available for the same LPAR during > online hours? > > Ron > > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of > > Dick de Groot > > Sent: Monday, April 06, 2009 11:13 AM > > To: [email protected] > > Subject: Re: [IBM-MAIN] MSU Change from batch > > > > Hi KevinI'm trying to have control over the number of MSU's an LPAR may > use > > overnight during the batch period to be sure that the online work will > not > > suffer from a high 4hr rolling average in the batch.So we want to change > at > > start of the batch dynamicaly the MSU value of that LPAR.(lower it). I > can > > change that on the HMC but I would like to use the API. to schedule the > task > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > -- Met vriendelijke groeten/With kind regards Dick de Groot ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
