Re: pwrdwnsys restart-yes did not restart

[John McKee <jmmckee@xxxxxxxxxxxxxx>]

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
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.