You probably want our ESASTR1 report that shows storage by group: User, DCSS/NSS, VDISK,
System execution, AddressSpace, MDC. and of course it shows the capture ratio, typically
99%, which means we know exactly where storage whent. other reports break down user
storage, dcss/nss storage, vdisk storage, mdc, addressspace, etc.
No, you can't lock an nss
James M wrote:
z/VM 5.2
Is there a way to see how storage is being used?
i.e. at any point in time who is using how much storage?
I can see this for each individual user via ind user.
I can see total via q stor
I can see trace via q traceframes
....but I don't see one command that "puts it all together"
How does one lock a nss (i.e. cms) into storage?
Is this advisable?
Filename=CMS Filetype=NSS Class=A Spoolid=1940
Time loaded=50 18:51 Size=6M
Pages: Main=687 Xstore=0 Dasd=261 Locked=---
Paging:
Xstore: Reads= 0 Writes= 0 Migrates=0
Dasd: Reads=10807 Writes=10058
Appreciate it!
