× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. May 2012

Re: best way to limit a job

On 16 May 2012 11:09, Thomas Garvey wrote:
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.

Why strive for inefficiency of work?

Suggestions?

Coded waits are pretty effective at ensuring reduction in use of the available CPU resource.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.