I agree with others that it would be better to assign a low priority to the job, then let the system allocate CPU, even if it consumes a much greater percent than other jobs. If you want to play tricks, you could add sleep() to the program; Chuck mentioned that. Other tricks would be to assign a time slice of 1 millisecond to the subsystem class, 1 max active threads in the subsystem. Constraining subsystem memory would probably work, but a bad idea; the only work getting done might be page-in, page-out.
From: Thomas Garvey <tgarvey@xxxxxxxxxx>
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, May 16, 2012 12:09 PM
Subject: best way to limit a job
I'm looking for the best and simplest way to limit how much of the system a
particular job will take. Ideally, we would be able to configure a job so
that it won't take more than x% of the CPU (as seen on a WRKACTJOB display).
We've tried using *CLS objects, defining Run Priority and Time slice
seconds, but it doesn't seem to limit the job. It still takes as much of
the CPU as it wants.
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact