suggesting a performance monitor is appropriate, but more appropriate is
pointing to the commands or screens of such that should be used in that
monitor to determine what was wrong.
Also, this is ALMOST a full-pack mdisk, it starts at cyl 1-end,not cyl 0
BTW: I am attempting to do this with DDR since I am about to clone 120
linux guests from the same set of mdisks, and I was going to run this in
parallel. But the ongoing production value is in the 6 mdisks that are
shared by hundreds of WAS guests.
Phil
Rob van der Heij wrote:
On Wed, Jan 27, 2010 at 10:02 PM, Phil Tully <tull...@optonline.net> wrote:
Is there something that will block an mdisk from being cached?
Yes, lots. Apart from the full pack disks as suggested, it's more
complicated than that. There's track- and record-MDC and differen
restrictions for being eligable. In most cases only reads are cached.
And some behavior will flush the entire mini disk from MDC. And CP
prevents a single user from monopolizing the resource, so users are
normally limited by how much that can insert at a given time.
Did I suggest a performance monitor to answer such questions... ;-)
--
'in media stat virtus'
Virtue's in the middle
