is supposed to point out a performance problem, and that is a good thing in my opinion, especially when migrating to z/OS 1.8, where the paging/swapping algorithm changed drastically. But:
1. The check indicates a medium severity exception. The actual Health checker message for this is an information only severity: HZS0004I/ILRH0207I , which violates the HC documentation. In addition, this wrong combination is not documented anywhere (that I could find), I only know about this because we had the 'problem' - just in case this was intended misbehaviour. The message combination should be HZS0002E/ILRH0207I. 2. The check still trips with a high frequency after adding another page data set, which is all a sysprog can do. That new page data set is filled first, the slot usage of the others doesn't change to get higher, which this check completely ignores for the next checking cycle. 3. Given that I want to be alerted when slot usage overall goes higher than 30% , I have kept this check, but once it had tripped, I have disabled this check via automation for the rest of the IPL (which I do not consider a good thing but the lesser of two evils). Barbara Nitz -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer ---------------------------------------------------------------------- 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
