×
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.
Gerald
I'm with you - everything has changed many times in the last 25 years, esp.
in re Work Management. Some faults have to happen, and the limits are much
higher in the newer processors. Have to go with the manual. As it says,
faults are less important than throughput. The more transactions for a set
number of faults, the less the faults affect each transaction. So the
measure is to take the total faults (DB & non-DB) / A->W state changes
(transactions) * 60 - if THAT > 20 and increases with additional users, you
MIGHT have a memory problem.
I used to think that hte best Work Management manual was the one for
System/38 - it still has the most extensive explanation of lots of things -
but things have changed - have to move along with them.
Last WM manual is for V4R5, still linked to at V5R2.
BTW, max recommended faults for interactive is 200! These are the
guidelines that Performance Adjust uses.
Also, I recommend using the version of the WM manual for the release of
OS/400 you are using - change, change, change!
HTH
Vern
At 05:20 PM 4/17/2003 -0400, you wrote:
Andy,
I'm not really trying to solve a problem. We are not using the performance
adjuster. All of Qinter runs in one pool - *INTERACT. My questions are the
result of a co-worker who states that if either the DB faults or NonDB fault
values ever goes above 20 then there is a problem with faulting. He's seems
to think the manual isn't relevant. I'm just looking for support that
there's more to measuring than just looking at the fault rates.
Gerald
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.
midrange.com
