If there is room, the cpu will be used. When things get tight, the RG cap will be enforced.
HTH, <snip> If you remember I had a situation where the CPU was hitting its four hour avg and soft capping itself. When this happens CICS and DB2 aren't allowed to flex above and I get max socket errors within the busiest CICS. At the advice of the group I set up a resource group and associated to a service class to batch jobs that I blame for running the service units up during the day initiating the capping. The resource group definition is CPU% based and I selected 20% max and 1 % min. Single jobs that are using this group regularly exceed the 20% max, multiple jobs really exceed the max collectively. Am I misunderstanding how this works? The goal was limit the number of SUs consumed by batch and spread it out longer in the day in hopes to avoid the capping. </snip> This email including attachments may contain confidential information. If you are not the intended recipient, do not copy, distribute or act on it. Instead, notify the sender immediately and delete the message. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
