As Bill noted, another excessive cull of relevant information to make the quote appear to suit your contention. My reference was to the AP(s) editting large dataset(s) leading to problems.
Local page size and count has *plenty* to do with it. I cleaned up one of our developers systems yesterday - a 6 Gig real system requires (currently) 18 entire mod-3's. Small(-ish) developers LPAR, no allocation above the bar - slot occupancy still above 10%. Some of us have to size for more than a single address space. Shane ... From: "Shmuel Metz (Seymour J.)" > >Mmmm - I'm surprised we haven't had some enlightened contributor > >suggesting that DASD is cheap, so just forget about USI, and throw > >page datasets at it. > > Why? The issue for below the line storage is not and never was DASD. > It doesn't matter how large or numerous your local paging data sets > are; you'll never have more than 16 MiB below the line and 2 GiB below > the bar, minus system overhead. ---------------------------------------------------------------------- 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
