We see such spikes caused by the WMQI Broker (or what is called these
days). At startup, it allocates a huge amount of storage (0.6 GB) per
address space (4 or 5), which is paged out for 90% after some time.
Caused us an aux storage shortage. And a subsequent haggle with IBM, as
their LE defaults
Ted MacNEIL [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]...
This was a while ago in a different age, prior to WLM and big real storage,
but I suspect the same situation could be a possibility.
..
This can still happen in GOAL MODE.
At the same time IBM introduced CPU-Critical,
of time, or after the first page-out they are unchanged pages and
move through a bit flick.
Ron
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Bob
Sent: Wednesday, 21 September 2005 4:59 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Short term paging
To all,
Thanks to all for good suggestions. I'e been looking at this some more and
the fact is that we were getting home grown page rate alerts due to a
couple factors.
1) Automation kicks off a bunch of stuff at 0500, 0530, 0600.
2) Our enterprising automation guy added a pagerate probe that
In a message dated 9/22/2005 7:54:59 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
say 5 min slowdown caused by a few ASIDS running
paging off the charts, a few days after the fact. Does Candle Omegamon
epilog keep that kind of detail?
RMF will report at RMF interval. Candle
-MAIN@BAMA.UA.EDU
Sent by: IBM cc:
MainframeSubject: Re: Short term paging
spike
Discussion List
To: IBM-MAIN@BAMA.UA.EDU
cc:
Subject:Re: Short term paging spike
To all,
Thanks to all for good suggestions. I'e been looking at this some more
and
the fact is that we were getting home grown page rate alerts due to a
couple factors.
1) Automation
99 @ LPAR @ 1500 TRKS = one week
Data available from 09/16/05 05.47.00 to 09/22/05 10.14.00 (present) which
is typical of the 7 to 8 days we usually see depends a little on activity
and has shrunk some with the recent addition of several very large storage
processors which also chewed up a good
On Thu, 22 Sep 2005 07:54:51 -0500, Bob H [EMAIL PROTECTED] wrote:
Mark,
I took a look at RMF III and that report shows current aux store usage by
asid, but only goes back an hour or so. I am still wondering the best way
for me to shoot a ... say 5 min slowdown caused by a few ASIDS running
You can use RMF II to monitor the system and write to SMF.
You need ASD(A,A).
Run the post processor and look for non-zero PIN RT.
Set the interval for around one minute.
Depending on the size of your shop, this should add 1-3% to your SMF data.
I've done this in the past.
-teD
In God we
I was thinking about a similar cause.
We see such spikes caused by the WMQI Broker (or what is called these days). At
startup, it allocates a huge amount of storage (0.6 GB) per address space (4 or
5), which is paged out for 90% after some time. A Stop/Start of the application
frees the paged
SMF 30 could also be used (working
set, but it would probably not be my first place to look.
...
Maybe not; it does have PIN data, though -- efficient if you are using interval
(of your choice) data.
-teD
In God we Trust!
All others bring data!
-- W. Edwards Deming
This was a while ago in a different age, prior to WLM and big real storage,
but I suspect the same situation could be a possibility.
...
This can still happen in GOAL MODE.
At the same time IBM introduced CPU-Critical, they introduced MEMORY-Critical.
This was due to a large bank in the US
On Tue, 20 Sep 2005 15:58:37 -0500, Bob [EMAIL PROTECTED] wrote:
I am seeing short term paging spikes (zOS 1.4 system) at around 6am. No
dumps happening, just a rapid drop in AFQ and then a spike of 500 pages /
sec... for a about 1 min.
Can anyone recommend how to find out who the causer is? Do
Last time I noticed something like this, we put it down to early
starters.
Online regions not getting used overnight, wound up getting (heavily)
trimmed. First arrival in the morning whacks the Enter key and (probably)
strolls off to get a coffee.
Different office, similar scenario, but hitting a
15 matches
Mail list logo
