I've heard of that some places are desperate to get every KB of extended private area they can, but I've never worked at one.
So usually I like to see between 50MB and 200MB of ECSA sitting around just in case. Then, if an ECSA hog comes along you have room to move. Such a "hog" (of varying degree) might be a new product you have to install which uses some ECSA, but these days you don't want to have to IPL to activate it, even in a test or development LPAR. I'd tend to agree that normally a GB of ECSA is too big. Also, I like to see the COMMON page data set big enough to back a fully populated CSA+ECSA, though some subpools of CSA are page-fixed, so I guess pages in these subpools will never be paged out. Cheers, Greg P. ---------------------------------------------------------------------- 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
