Bob, Have you taken a look at Chapter 2 in the "z/OS Init and Tuning Guide"?
It really does a good job of explaining the aux storage manager and the size and usage of local page datasets. If you have a system tool like Sysview (or MXI, RMF, Omegamon, Mainview..etc etc), you can observe the aux storage usage by ASID or page dataset and then refer back to the documentation to help understand what is going on in your system. Rob Scott Rocket Software, Inc 275 Grove Street Newton, MA 02466 617-614-2305 [EMAIL PROTECTED] http://www.rs.com/portfolio/mxi_g2 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Robert Pelletier Sent: 07 March 2007 08:51 To: [email protected] Subject: Re: Paging and SLOTS (was: Why are they so full ? RE: When Does the New LOCAL Get Used? RE: ILR006E COMMON PAGE DATA SET FULL,...) Thanks Adam. Does having only 256meg for the machine result in more paging? Have a Nice Day ! Bob Pelletier Connecticut Student Loan Foundation Rocky Hill, Ct. -----Original Message----- From: Gerhard Adam [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 06, 2007 4:31 PM To: [email protected] Subject: Paging and SLOTS (was: Why are they so full ? RE: When Does the New LOCAL Get Used? RE: ILR006E COMMON PAGE DATA SET FULL,...) > I just can't figure out why one TSO user might have 10 slots and >another has 0: Paging is ultimately a function of storage saturation, so whenever z/OS has to dynamically acquire more pages to hold in reserve (the Available Frame Queue), then the Real Storage Manager (RSM) will go out and locate the "oldest" pages and move them to auxiliary storage. So, in a nutshell, the longer you are running and the longer you are holding a large working set, the greater the likelihood that some of your unreferenced storage will become a candidate for "page-out". Similarly if an address space gets physically swapped out, there is a good possibility that some of the working set pages may not be referenced and therefore, not be paged back in. None of this is particularly significant unless the pages that were removed become necessary in storage. If there is a perpetual page-out, then page back in type of activity then this can create performance problems which need to be addressed. Hope this helps Adam ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
