David Andrews pisze:
[...]
- Shared catalog volumes kill you. Don't have
multiple catalogs on the same volume. Don't have
catalogs on shared volumes, period. In the latter
case every catalog lookup requires a VVR read,
regardless of whether the
I agree, I don't see any reason to not put the catalogs on the same drive.
Maybe when there were still real drives, it might have made a difference,
but with the arrays that most people are using, I would imagine that it's
not really going to make a difference.
I actually have some issues with
We are currently reviewing all of the ICF catalog definitions in our shop. All
of our catalogs are ECS defined.
Any best pratice or considerations with regard to the following catalog
performance options beyond the defaults when these are not specified?
STRNO
BUFND
BUFNI
FREESPACE
RECORDSIZE
considerations with regard to the following catalog
performance options beyond the defaults
Eileen McClintock has done a presentation at SHARE about catalog tuning.
See if you can find it. She recommended (in 2007), among other things:
- Don't use anything larger than 8K CI size;
There was a feature for AUTOTUNING but back in 2008 IBM recommended
turning it off (OA20748).
I'm not sure if the issues were ever resolved but OA25072 09/2009 turns
it off and disables enabling it.
F CATALOG,REPORT,CATSTATS should show what is currently in use.
-Original Message-
John
On Mon, 17 May 2010 12:46:42 -0400, David Andrews d...@lists.duda.com wrote:
Eileen McClintock has done a presentation at SHARE about catalog tuning.
See if you can find it. She recommended (in 2007), among other things:
- Shared catalog volumes kill you. Don't have
multiple
On Mon, 2010-05-17 at 15:09 -0400, Mark Zelden wrote:
I think you are referring to VVDS mode sharing. If you have the catalog
in ECS mode, the above isn't true.
As an aside, it's a little difficult to avoid sharing catalogs between systems
these days. :-)
My notes were from a
7 matches
Mail list logo
