<snip> What would be a "comfortable" paging subsystem configuration, especially for the Production LPAR, as to individual size and (especially) number of page datasets? </snip>
IMO, the "largest needed" paging subsys can be determined as follows: 1) Determine actual working set in use. This is easy if you are not currently paging, just look at the RMF reports. IIRC, paging follows a square root algorithm. i.e. double the working set, the page rate goes up by sqrt(2). 2) convert the working set determined in step 1 above to gigabytes 3) divide by 0.3 (the block paging algorithm declines in efficiency after page ds utilization exceeds 30%) 4) allocate sufficient full volume local page ds' to contain the number determined in step 3 using about 2.5 - 2.8 gig per 3390M3 volume. 5) sprinkle the local page ds's over as many paths and channels as practical. See Sam Knutson's post on this. Of course, this method is only as good as the determination of the working set. ---------------------------------------------------------------------- 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
