Cross-posted from MXG-L (and extended)
The RMF guide describes the "Working Set" to include frames backing Dataspaces and Hiperspaces. I assume the "Frame Occupancy" does only include address space frames. Is this correct? The RMF manual is not clear about this. My assumption is based on the fact that I do see entries with much higher "Active Frames WSET" than "Frame Occupancy", and I do know that the job is using Dataspaces. Are shared Dataspace and Hiperspace frames counted for the onwing address space, only? Assume address space A (AS-A) creates some Dataspace (DS-A) and shares it with AS-B. AS-A stores 2MB of data into DS-A. At that time 500 frames are assigned to the Dataspace and counted in AS-A's WSET number. Assume some frames get stolen from the Dataspace. Some time later, AS-B accesses the all data in DS-A, i.e. all 500 frames are needed, leading to page-in of the once stolen pages. To whom are those frames accounted? True or False? - The ones not stolen had been counted for AS-A when AS-A initially wrote into DS-A. - The ones not stolen are *not* counted for AS-B when accessing DS-A. - The ones now paged-in are counted for the *owing* AS-A. - The ones now paged-in are *not* counted for AS-B when accessing DS-A. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
