RE: best way to limit a job -- MIDRANGE-L

× 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.

When I moved to the AS/400 years ago (from IBM mainframe) one of the first things I was taught was not to think the same way about CPU %. If the machine has it available why not let a job have 100%? As long as the mix of jobs are playing well together (job priority, memory, etc) it's best to let each job take as much as it can.

Or am I misunderstanding what you're trying to accomplish?

Scott Lindstrom

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Thomas Garvey
Sent: Wednesday, May 16, 2012 1:10 PM
To: 'Midrange Systems Technical Discussion'
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.

Suggestions?

Tom Garvey

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.