What you have done is correct. You do not necessarily want to restrict time slice to much as that will cause unnecessary paging. You want to give it a higher Run Priority Number. Say 99. It will still use all unused CPU but release the CPU if some other job needs it. Running a system at high CPU but sub-second response time is good use of resources. Batch jobs should have the lowest priority, (highest run priority number), that any server or interactive jobs. If this is a special known long running job, you can even put it behind normal batch jobs.

Remember it does tie up a subsystem entry. So you subsystem must allow enough jobs and you job queue entry must allow enough jobs, else you wonder why other jobs are stuck on queue.

This thread ...


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

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 [javascript protected email address].