×
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.
putting the job in a special subsystem will allow limits on memory,
but I have not done much with work management lately so this
is my 2 cents...
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Thomas Garvey
Sent: Wednesday, May 16, 2012 12: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 is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
