Sorry, "Scott covered most of this ..."
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Scot covered most of this - most importantly the need to inspect the workloads
on the LPAR(s) of interest.
Despite being for DEVL, the latter report is better as the machine is now busy.
So let's turn the question around:
Q: Is PROD getting all the CPU it wants ?.
A: YES.
The weights indicate y
email: martin_pac...@uk.ibm.com
Twitter / Facebook IDs: MartinPacker
Blog:
https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker
From: Anne & Lynn Wheeler
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 01/10/2014 20:16
Subject:Re: zOS 1.13 – CPU latent demand
Sen
1985? You're just a young'un.
-
-teD
-
Original Message
From: Martin Packer
Sent: Wednesday, October 1, 2014 15:20
To: IBM-MAIN@LISTSERV.UA.EDU
Reply To: IBM Mainframe Discussion List
Subject: Re: zOS 1.13 – CPU latent demand
FWIW the vast majority of my customer set have multiple
...@uk.ibm.com
Twitter / Facebook IDs: MartinPacker
Blog:
https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker
From: Anne & Lynn Wheeler
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 01/10/2014 20:16
Subject:Re: zOS 1.13 – CPU latent demand
Sent by:IBM Mainframe Discus
gib...@wsu.edu (Gibney, Dave) writes:
> In my opinion, back in the day, there as a benefit of going to
> fewer/faster engines. But, with a deep drop off a precipice when fewer
> reached one.
>
> Never again will I willingly agree to be on a single CPU machine.
in the past, multiple engines have be
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Scott Chapman
> Sent: Wednesday, October 01, 2014 6:08 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: zOS 1.13 – CPU latent demand
>
>
Snip
>
As Martin mentioned, "unaccounted" could be multiple things. However, from the
reports you've shown, my first guess would also be that it's likely related to
CPU contention.
However, I would start by looking at RMF III's DELAY, PROC, and ENCLAVE (if
we're talking about DDF threads) and looking
Thanks for the reply Martin. I have checked paging and it is very low.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
014 14:43
Subject:Re: zOS 1.13 – CPU latent demand
Sent by:IBM Mainframe Discussion List
Thanks for the reply Scott. You are correct, we only have 1 CPU. We have
many DB2 threads with high "unaccounted for time". One of the possible
reasons for this could be th
Thanks for the reply Scott. You are correct, we only have 1 CPU. We have many
DB2 threads with high "unaccounted for time". One of the possible reasons for
this could be that zOS/DB2 is waiting on CPU. I was hoping to use the CPU
Activity report to determine if this is contributing to "unacc
It appears you have a single CP. If the CPU is busy on one of the other systems
when PROD wants to be dispatched, it will have to wait for the other system to
give up the processor or for PR/SM to steal it away. My guess is that's why
you're seeing what you're seeing that, and my inclination is
On 09/27/2014 01:36 AM, Shane Ginnane wrote:
> As a distraction from the shellshock sideshow,
>
> On Fri, 26 Sep 2014 15:54:05 +, Gary Snider wrote:
>
>> I am trying to understand how to utilize the RMF CPU report so that I can
>> evaluate utilization of our CP and latent demand.
> Tread with
As a distraction from the shellshock sideshow,
On Fri, 26 Sep 2014 15:54:05 +, Gary Snider wrote:
>I am trying to understand how to utilize the RMF CPU report so that I can
>evaluate utilization of our CP and latent demand.
Tread with care - there be dragons.
RMF is a sampler - on such a li
Hello,
I am trying to understand how to utilize the RMF CPU report so that I can
evaluate utilization of our CP and latent demand. The publications on this
report I have read, indicate that when LPAR Busy < MVS Busy, this is an
indication of latent demand. In the report below, this is the ca
15 matches
Mail list logo
