>What does this exactly mean: "freemained frames"? Is it just a counter or do >they refer to specific frames, that are kept at hand in the address space for >faster assignment of new frame requests? > >I am not surprised that those frames, if they are "available" at all, are not >accessible anymore and access is punished with the same 0C4 as any other not >getmained frame.
See OA46291. The APAR is for z/OS V2.1 and V1.13, it is in the base for z/OS V2.2. With this new function, RSM (SRM?) may decide *not* to free the frames that are backing some virtual area upon a STORAGE RELEASE or FREEMAIN. It is a significant change, IMHO, since a program might continue to (erroneously) access storage that has been freed but *not* getting an S0C4-10/11 because the frame is still assigned. Or, it may get an S0C4-10/11 at some later point if RSM decided to really free some such frame at a later time. I do not want to build on that function to cheat. I'm wondering what information a dump would reveal in such a case. What would VSM tell me? etc. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
