/snip We lost a production system a while back because of a spin loop in RSM. Apparently RSM needed some storage, but before demand paging operations could complete, the system got partitioned out of the sysplex for lack of heartbeat activity.
IBM pointed us to OA12185, which recommends this value for available frame queue: MCCAFCTH=(4000,4500) . What's startling about this recommendation is that it's ten times (!) the default value of MCCAFCTH=(400,600) . We're concerned that such a high value will increase paging rates considerably. Maybe it's overkill. Any thoughts? /snip/ You might want to look at APAR OA14318 (open -ANALYSIS) also. We run a NON-IBM sort product that caused/was implicated in several SPIN LOOPS until we changed some internal sort options.... ---------------------------------------------------------------------- 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
