The person complaining is a high level person who someone misguidedly showed
how to do a 'wrkactjob' and worse still, position the cursor over the CPU%
column and press F16 to resequence. Education has not helped. I've tried
all kinds of analogies to no avail. The job taking the most CPU must be
misbehaving and consuming all his resources.
Thanks for all the advice to all responders.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Musselman, Paul
Sent: Thursday, May 17, 2012 4:21 PM
To: Midrange Systems Technical Discussion
Subject: RE: best way to limit a job
You could create a separate subsystem, with a fixed memory pool (so you can
allocate just so much memory), a single-threaded job queue, and let no other
jobs run in that subsystem. Then play games with time slices and run
priorities to hamper the job as much as possible!
Yes, it 'wastes' that pool of memory (can't be shared), but it might be the
only way to throttle the job to less than X%. Of course, if nothing else is
running, even a time slice of "1" will end, the system will check for other
work to do and pop back to that job anyway, and you're back to square one.
Is the person who complains about the job 'hogging' the system the same
person who gets the report? Maybe you can get the job's owner involved in
the political process and let him know that "Mr. Client" is limiting the job
just so it doesn't 'take over' the system. Maybe this user can be taught,
and then train Mr. Client!
Paul E Musselman
Paulmmn@xxxxxxxxxxxxxxxxxxxx
--
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
