|
CP QUERY DASD DETAILS ccuu will display the disk size Example: q dasd details 2630 2630 CUTYPE = 3990-E9, DEVTYPE = 3390-0A, VOLSER = 310RES, CYLS = 3339 CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY -SUBSYSTEM Y Y Y - N N -DEVICE Y - - Y N N DEVICE DETAILS: CCA = 3A, DDC = -- DUPLEX DETAILS: --
This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.
-----Original Message-----
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.... --
|
Title: DASD sizes and extended memory usage...
- DASD sizes and extended memory usage... Nix, Robert P.
- Re: DASD sizes and extended memory usage... Rich Smrcina
- Re: DASD sizes and extended memory usage... Imler, Steven J
- Re: DASD sizes and extended memory usage... Romanowski, John (OFT)
