Hi Walter,
You are right, our capture ratio went down to 60% at the time of the
problem. Thanks for pointing this to me.
Regards,
Jason.
Quoting Walter Medenbach <[EMAIL PROTECTED]>:
Sounds like uncaptured cpu and therefore is not an error with RMF and TMON.
Uncaptured cpu is cpu that has
The following message is a courtesy copy of an article
that has been posted to bit.listserv.ibm-main as well.
[EMAIL PROTECTED] (Jason To) writes:
> We have encountered some weird problem last week and discovered that
> the total MVS CPU busy percentage reported by both RMF and TMON were
> inaccu
Behalf Of Walter Medenbach
Sent: 08 Januarie 2008 05:36
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Inaccurate CPU% reported by RMF and TMON
Sounds like uncaptured cpu and therefore is not an error with RMF and
TMON.
Uncaptured cpu is cpu that has not been associated with a particular
address
space. Your
Sounds like uncaptured cpu and therefore is not an error with RMF and TMON.
Uncaptured cpu is cpu that has not been associated with a particular address
space. Your capture ratio appears low. Find out when the problem started and
whether it occurs 24x7. Look for such things as SLIP traps or high p
We have encountered some weird problem last week and discovered that
the total MVS CPU busy percentage reported by both RMF and TMON were
inaccurate. RMF and TMON reported MVS CPU percentage does not match
with the total CPU% usage by the jobs running in the system at least
in one LPAR, the
5 matches
Mail list logo
