RE: best way to limit a job

I'm in complete agreement with Chuck on this: "Why strive for inefficiency
of work?"

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.

No, you are not looking at it correctly; it takes what's available, and you
wouldn't want it any other way! What would be the purpose of preventing a
job from using resources that aren't needed at the moment by any other
process? Maybe I just don't understand.

As others have stated, give the job a high run priority ( CHGJOB RUNPTY(
_big_number_like_90_ ) ) instead. One of the special skills of System i
(and its predecessors all the way back to S/38) is its ability to manage
workload. It's been the best in the business at that for 35+ years!

On the other hand, if you still want to cripple or severely limit the job's
performance, you may want to convert it to use Windoze.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"When I was a boy of fourteen, my father was so ignorant I could hardly
stand to have the old man around. But when I got to twenty-one, I was
astonished at how much he had learned in seven years."
-- Mark Twain