samb01 wrote:Now, i am thinking about a solution with the automate TWS. Actually, the jobs run at the same time. (07h00 pm). I think it's not very good for the CPU. So i want to run job ten by ten (for example, or 20 by twenty) every hour. Mays be it's better for the CPU and the capping of the machine ?
I'm not convinced this is the correct solution for your problem, but if you do want to go down this route then TWS has a built-in feature to limit the number of jobs running in a certain time frame. You need to add a special resource to the job and then define the special resource in the database with a MAX Usage Limit. When this limit is reached, the resource will be unavailable and no further jobs can start. Schedule a job to run at the end of the interval to issue a SRSTAT command to make the resource available again.