An earlier append (properly) berated IBM for not providing SMF information
about 2G usage.
We have every intention of addressing that in the near future.
Peter Relson
z/OS Core Technology Design
--
For IBM-MAIN subscribe /
In a message dated 11/9/2005 6:36:25 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
We have every intention of addressing that in the near future.
Mark and Roland did it about 4 hours(with a couple of snags
and enhancements thrown in). If you can't measure it, you can't
If you can't measure it, you can't tune it.
...
The original quote was more general:
“If you can't measure it, you can't manage it”.
“Tuning” is just one aspect of “Managing”.
-teD
Me? A skeptic? I trust you have proof!
--
From: Peter Relson
Time to enflame the waters...
I've been away for a couple of days. Seems this didn't even register a bite.
Time for me to rectify that oversight.
There is absolutely nothing wrong, incorrect, improper, or unexpected
about
any system space (GRS) using as much memory above
I am differentiating GRS from DB2 in this regard.
One thing to remember: DB2 is already (in most shops) using HIPERPOOLs (even in
64-bit mode).
What V8 will do is move all of those into its own adress space.
So, you are alread back-stored in AUX.
What the issue is, what happens when the DBA
On Fri, 4 Nov 2005 23:01:39 +1000, ibm-main [EMAIL PROTECTED] wrote:
There is absolutely nothing wrong, incorrect, improper, or unexpected
about
any system space (GRS) using as much memory above 2G as it wants,
provided
that it has documented that use so that customers can properly plan.
Note
Time to enflame the waters...
There is absolutely nothing wrong, incorrect, improper, or unexpected about
any system space (GRS) using as much memory above 2G as it wants, provided
that it has documented that use so that customers can properly plan. Note
that I am differentiating GRS from DB2 in
If the system needs the storage to do its job, then it needs the storage
(emphasis on needs).
And all that you would do is break the system by trying to impose a limit where
none should be imposed.
...
Peter,
A very valid point.
And, in DB2's, case it was not a secret.
And, it is “needed”;
On 11/2/2005 7:57 AM, Barbara Nitz wrote:
Doubting what
showzos told me, I took a dump, learned a new IPCS command and found that
59 frames are used, 3300 are on AUX, more than 112000 are FREF (meaning
getmained but unused) and 408000 are in the guard area.
I don't think you actually have any
what is showzos and what ipcs command did you use.
Walt Farrell [EMAIL PROTECTED]
Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
11/03/2005 12:05 PM
Please respond to
IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu
To
IBM-MAIN@bama.ua.edu
cc
Subject
Re: MEMLIMIT and IEFUSI
Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Anthony Bongiorno
Sent: Thursday, November 03, 2005 7:07 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: MEMLIMIT and IEFUSI and GRS
what is showzos and what ipcs command did you use
Well, I just ran Rolands new showzos on both z/OS 1.4 and 1.6.
For 1.4, all is well with the world (except for what we already knew and
IRLM also hardcodes the memlim with 2GB).
In 1.6, not only does GRS overwrite the MEMLIMIT with 64PB, it also has 4
objects allocated above the bar with 19GB
On Wed, 2 Nov 2005 13:57:07 +0100, Barbara Nitz [EMAIL PROTECTED] wrote:
For 1.4, all is well with the world (except for what we already knew and
IRLM also hardcodes the memlim with 2GB).
Here is what my testing told me:
DBM1 gets 4T no matter what (unless it can get MEMLIMIT=NOLIMIT via
13 matches
Mail list logo