On Sat, 2 Aug 2008 19:25:29 -0500, Jim Marshall <[EMAIL PROTECTED]> wrote:
>Had an outage in the middle of this week due to the following reported to me: > >"IBM completed its analysis of the dump shipped and concluded the problem is >associated with APAR OA23299. APAR OA23299 is associated with long >running enclave that has been active for weeks in a service class with >response time goals such as WebSphere Application Server. Apparently, this >can cause a negative index value and an overlay of storage." > >Seems to me the LPAR had gone about 4+ weeks or more without being >IPL'ed. The appearance of it made us think it was some problem in device >support associated with PPRC (which we do not run) or maybe SRDF-A. > >Until the APAR can be applied, we took the outage early Sunday morning to >reboot all the LPARs and will each Sunday. > >Jim (WashDC) > Does this mean that I need to stop my car on a long-duration trip every ??? miles, just in case there might be a software glitch waiting to happen? Given legacy methodologies and "data center procedures", I can only imagine explaining to today's end-users that they cannot work on a particular day, simply because of an IPL or other outage or because we're running backups, "just because that's the way we do things." Come on, we're no longer living in the Bedrock era, Barny. This is so "swatting at flies with a Buick", people. Scott Barry SBBWorks, Inc. ---------------------------------------------------------------------- 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
