Just a follow up. I set the BOC to correct GMT/UTC (was about 40 seconds fast).
DEACTIVATEd my LPAR that uses SIMETR (unique in the CPC, this LPAR is part of single system PLEX). ACTIVATEd the same LPAR expecting it to get the 'new' time from the BOC (it didn't). Can anyone confirm/deny that in order to refresh the time from the BOC the CPC (rather than just LPARs) would have to be DEACTIVATE/ACTIVATE (essentially a POR)? I run 5 LPARs, 4 in one BASIC PLEX with same SIMETR and the 5th is single system BASIC PLEX with a different SIMETR. Thanks to all Ken Porowski AVP Systems Software CIT Group E: [EMAIL PROTECTED] -----Original Message----- Porowski, Ken A question just came up from my Information Security dept. about setting and synching the Mainframe clocks. We generally reset them whenever we have a full system shutdown and don't worry about it otherwise but they now want a procedure to regularly correct clock drift. Please correct me if I'm wrong Hardware Clock - Set via HMC/SE to (In my case) GMT/UTC. TOD Clock - Set from Hardware clock at LPAR Activation time, not synched to hardware clock after then. SIMETR - Set from TOD clock by first LPAR referencing it. All other LPARs with same SIMETR will have same time reference. The only way to 'correct' GMT/UTC clock drift in a plex using SIMETR would be to Deactivate all LPARs (using the same reference) then Activate to get new TOD/Hardware reference. If using an ETR (9037) TOD clocks are continuously (FSVO continuous) synched to the ETR and a change to the ETR GMT/UTC setting will be propagated to all referencing LPARs without need for Deactivation/IPL. Thanks all. Ken Porowski ---------------------------------------------------------------------- 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
