On 03/02/2012 06:44 PM, Charles Mills wrote:
And the answer from those who know is
"It happened during the POR last Thursday and we're talking with IBM to
figure out why a POR would do that to us."
Thanks all for your patience with YATQ (yet another time question).
Charles
In absence of sysplex timer or the like, the processor TOD clock is set
only at POR and is set based on the HMC clock, which may in turn sync
once a day with the SE clock. If you don't have any procedure to sync
the HMC/SE clocks to UTC or verify they are reasonably accurate when you
know a POR is imminent, odds are they have drifted from reality and a
POR will propagate that error to the processor TOD clock, which in turn
propagates to all LPAR TOD clocks as they are activated. It would seem
your operators must be setting local time explicitly at IPL (rather than
using a fixed offset from TOD), or the error would have been more
obvious after the IPL.My recollection is it has worked this way ever
since IBM mainframes have had HMCs for control.
--
Joel C. Ewing, Bentonville, AR [email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
