A quick answer is to just count REAL. AUX stays because it doesn't know if the page it represents was modified. Let's just take a single page.
It gets paged out. Sometime later it gets paged back in. If it become a candidate for page stealing again, and it hasn't been modified, it just gets stolen. This way paging is reduced and AUX manager is mostly kept out of it. Chris Blaicher Senior Software Engineer, Software Services Syncsort Incorporated 50 Tice Boulevard, Woodcliff Lake, NJ 07677 P: 201-930-8260 | M: 512-627-3803 E: [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ken Porowski Sent: Monday, July 30, 2012 2:25 PM To: [email protected] Subject: Working Set = Real Frames + Aux Slots? If I want to know the working set size of a task can I just add real storage frames in use and aux slots in use? Or is an aux slot not released until freemain or end of task? For example taskA is using 100 real storage frames then gets swapped out so 100 aux slots are used then is swapped back in. Do I now have 100 real frames and 100 aux slots? Yes I know that not all 100 frames would be sent to aux, just trying to keep the example simple. I am attempting to track gradual storage growth across many tasks. Up until last week we never paged so aux in use was zero for most asids. Something happened (not sure what yet) and lots of asids were stolen from with resulting usage of aux. Now when I add real + aux I see much higher allocation than before aux usage. TIA Ken Porowski -------------------------------------------------------------------------- This email message and any accompanying materials may contain proprietary, privileged and confidential information of CIT Group Inc. or its subsidiaries or affiliates (collectively, "CIT"), and are intended solely for the recipient(s) named above. If you are not the intended recipient of this communication, any use, disclosure, printing, copying or distribution, or reliance on the contents, of this communication is strictly prohibited. CIT disclaims any liability for the review, retransmission, dissemination or other use of, or the taking of any action in reliance upon, this communication by persons other than the intended recipient(s). If you have received this communication in error, please reply to the sender advising of the error in transmission, and immediately delete and destroy the communication and any accompanying materials. To the extent permitted by applicable law, CIT and others may inspect, review, monitor, analyze, copy, record and retain any communications sent from or received at this email address. -------------------------------------------------------------------------- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ATTENTION: ----- The information contained in this message (including any files transmitted with this message) may contain proprietary, trade secret or other confidential and/or legally privileged information. Any pricing information contained in this message or in any files transmitted with this message is always confidential and cannot be shared with any third parties without prior written approval from Syncsort. This message is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any use, disclosure, copying or distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or Syncsort and destroy all copies of this message in your possession, custody or control. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
