OK, apparently this was far from over last time I posted. Sorry for not posting sooner, but I have been hardly getting sleep trying to get to the bottom of this. Seems there was a large scale failure of power supply at the facility. I have tried to understand the exact reason as detailed by the guy in charge of the power infrastructure (believe me, he also tried to explain). Anyway, it took them a week to eliminate potential causes, and they had to perform major changes to the infrastructure before they figured it out. Finally, after running the system for half a day, it seems that the problem is solved. Good thing the production is located at a different facility...
----- Original Message ----- From: peter novack Sent: 07/16/12 06:42 PM To: IBM Mainframe Discussion List Subject: Re: Urgent help needed - Message ISN000E OK, here's the story so far: We've tried IPLing a few times, and later performed a power-on-reset, but still got the message a few hours later. Unfortunately, they do not have official IBM support (assuming they would even support such old machines), and I don't think that's about to change, given the ongoing migration to open systems. I still can't find anything interesting in the logs and I am running out of ideas. The only thing we could think about that might be related is a power failure we suffered a day before the message appeared for the first time. ----- Original Message ----- From: peter novack Sent: 07/16/12 06:21 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Urgent help needed - Message ISN000E Hi all, I work as a consultant in a small installation in Eastern Europe. Their main business activity runs on a couple of Z900 machines (z/OS 1.6). One is for production and the other for development. Like many organizations, they've been trying to get rid of the Mainframe for years now, so far with very little progress... A few hours ago, we got a very strange message on the development machine: "ISN000E The service processor has failed. Some critical system functions are inoperative. An orderly shutdown of the entire system should be planned in order to minimize the possible impact of this failure." I thought I might be able to find something that might explain this in the syslog, but it showed nothing out of the ordinary. We tried IPLing but got the error message again. After a short (and rather panicked) discussion with the operations manager, and considering the documented instruction to shut down the system, we've decided to take down all LPARs. Naturally, they are ve ry disturbed about this message, and the required system shutdown that followed. Any thoughts on what might be causing this? My client and I would highly appreciate any hints/tips on the root cause of this... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
