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



If the system in question is averaging 45% cpu,
it sounds more like a user problem than one
that requires work management.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Thomas Garvey
Sent: Wednesday, May 16, 2012 1:46 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: best way to limit a job

I understand that a system running at high CPU utilization is not a bad thing, but my clients don't necessarily see it that way. They do a wrkactjob and see some job taking 45% of the system and they think something else must be waiting. I can instruct them, train them, inform them, etc but they still don't want job x taking more than x% of their CPU.
This is especially important to those clients who can consume more than 100%. How do you explain that your job isn't taking THEIR job's resources?

I've tried run priority of 75. Guess I'll have to move it up to 95 or 98.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dennis Lovelady
Sent: Wednesday, May 16, 2012 2:05 PM
To: 'Midrange Systems Technical Discussion'
Subject: 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



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



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




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.