Re: pwrdwnsys restart-yes did not restart

I would think that would throw a SRC code to the front panel (but all things are
possible, and I've gotten the story 3rd hand so possible there was a src).
They have asked me if anything to do to make sure it doesn't happen again.
The first thought is not to ipl... not really needed.
Jim



----- Original Message ----- From: "John McKee" <jmmckee@xxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Sunday, May 06, 2012 8:30 PM
Subject: Re: pwrdwnsys restart-yes did not restart

This is ancient history, I know. But, it makes me wonder if different
things happen during an IPL depending on how it was initiated.

Over twenty years ago, I was called when the weekly IPL of the B50
failed. Turned out that the box with mostly 9335 and two 9332 DASD
usints failed to restart with the same command, but came up just fine
if the power switch paddle was moved to ON.

IBM CE told me one of the drives took "too long" to spin up so the IPL
was aborted by the service processor. The 9332 DASD had gotten close
to the MTBF. What I recall was the bearings were beginning to fail.
I don't recall the timing, but somewhere in that period, the CE called
stating he needed to replace the load source and would be onsite in an
hour.

So, I wonder if something like this could be happening.

John McKee

On Sun, May 6, 2012 at 7:08 PM, franz400 <franz400@xxxxxxx> wrote:

Other than a posting in 2008, has anyone else had this?
This machine ipls unattended every Sat night without fail, except this
Sat.
PWRDWNSYS option(*IMMED) restart(*Yes)

It's an E4A in a tower (not rack). Has the IBM UPS (from Eaton?)
DSPLOG shows no entry after QSYSARB3 ended (when seems a normal end).

IBM had them press button to ipl.
No mention of a src code.

Next entry in log is the ipl after IBM was called.
Did a normal startup.

Any ideas?
Jim Franz