new with 1.7 and up. In my opinion falls into the category 'stupid check, written under duress'. Reasons:
1. XES does 'structure full monitoring'. It is turned off deliberately in the structure definition (FULLTHRESHOLD=0) because if the structure gets full, logger better offload the logstream data thus freeing the space in the structure, especially if there is a one-on-one relation between structure and log stream. The XCF messages that indicate a structure full just before offload occured were a pain when the operator called at oh:dark:30. 2. XES does checking for entry-to-element ratios. This is turned off deliberately for all list structures in the structure definition (ALLOWAUTOALT=NO) due to XESs indiscriminate changing of ratios and thus removing full signalling connectivity between systems. Yes, I know that this is not a signalling structure, but what do I know what the side effects are if I let XES have free rain (aside from destroying full connectivity for signalling structures)? 3. Abysmal documentation in the health checker book. The sdsf screen was slightly better. 4. What does LOGR care about structures in the first place? It should offload when it detects these conditions and not report about things that are in its own power to prevent. (And the structure that was flagged had the default highoffload threshold of 80%). 5. Why isn't there intelligence to see that soemthing was deliberately turned off via policy, *if* LOGR wants to check it at all? Barbara Nitz -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger ---------------------------------------------------------------------- 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
