Hi, Rob, So this indicates that the SYSTEM virtual address space has 1 page on pag ing DASD, but how do we know it's the one remaining page on the specific volu me Martha's trying to drain? If you folks have solved that one, I'd be quit e interested in hearing how. ;)
I guess if you go through all spaces (for the system and for all users), and only ever find one page on DASD total, then you can safely assume it's th e one, but otherwise, I don't see how it helps. - Bill Holder z/VM Development, IBM On Fri, 9 May 2008 06:47:03 +0200, Rob van der Heij <[EMAIL PROTECTED]> wrote: >On Thu, May 8, 2008 at 8:39 PM, Bill Holder <[EMAIL PROTECTED]> wrote: > >> The problem with scanning the PGMBKs is, of course (in addition to the re >> being lots and lots of them), that PGMBKs are themselves pageable, and so > >Fortunately they run a performance monitor that makes the job a bit easi er. > >My apologies for those with proportional font, but the 1 for the >address space SYSTEM tells me who got his page out there. > > <-----Address Space Pages-----> > <Resident> <Locked-> <PagedOut> >Owner Space Name <2GB >2GB <2GB >2GB DASD XSTOR >-------- ------------------------ ---- ----- ---- ---- ---- ----- >System: System 31K 3266 0 16 1 0 > Virtual Disk_Subset 0 0 0 0 0 0 >SYSTEM FULL$TRACK$CACHE$1 0 0 0 0 0 0 >SYSTEM ISFCDATASPACE 0 36 0 16 0 0 >SYSTEM PTRM0000 31K 0 0 0 0 0 >SYSTEM REAL 0 0 0 0 0 0 >SYSTEM SYSTEM 0 3106 0 0 1 0 >MAILER VDISK$MAILER$$$0200$0044 0 0 0 0 0 0 >SYSTEM VIRTUAL$FREE$STORAGE 0 124 0 0 0 0 > >I recall that CP used to push something like 544 pages during IPL >(initialization stuff) and while that seems gone these days, this >single page may still be part of that process. > >Rob >-- >Rob van der Heij >Velocity Software GmbH >http://velocitysoftware.com/ >======================== ========================= ========================
