0AD4 CUTYPE = 3990-E9, DEVTYPE = 3390-0C, VOLSER = LOAN34, CYLS = 10017
CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY
-SUBSYSTEM Y Y Y - N N
-DEVICE Y - - Y N N
DEVICE DETAILS: CCA = 3A, DDC = 20
DUPLEX DETAILS: --
Ready; T=0.01/0.01 12:42:54
Computer Associates
Senior Software Engineer
Work: +1 703 708 3479
Fax: +1 703 708 3267
[EMAIL PROTECTED]
[EMAIL PROTECTED]
From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Nix, Robert P.
Sent: Friday, November 18, 2005 12:39 PM
To: [email protected]
Subject: DASD sizes and extended memory usage...
Two questions:
Is there a way, using VM commands, such as query ccuu, to find out the size of a real disk. I can run ICKDSF, but then I have to get to a full pack minidisk or attach the real device, so that's not really too useful. Anything else that might do the trick? We have an eclectic mix of mod 3, mod 9, mod 27 and mod 54 devices, and address range doesn't really bound them.
Second: I got our hardware admin to allocate some of the memory in my LPAR as extended. I can see MDC usage of it, but how would I go about finding out if any of it is being used for paging? I haven't found a command that would indicate that any paging was going there....
--
Robert P. Nix
Mayo Foundation
RO-OC-1-13 (new
loc) 200 First
Street SW
507-284-0844
Rochester, MN 55905
-----
"In theory, theory and practice are the same,
but
in practice, theory
and practice are different."
