On Fri, Jan 30, 2009 at 9:07 AM, Florian Bilek <[email protected]> wrote:
> 1.) The SET VTOD command does not accept parameters such as current time > -1h. This is quite problematic since we will always have a small difference > from the hardware clock depending how exactly the operator entering the time > and hits enter. It would have been practical for such cases as yours to be able to specify the offset rather than the time. Especially since under the hood, there's a field VMDEPOCH in the VMDBK of the user. That specifies the offset of that user's virtual TOD and the "real TOD" as CP has it (which again is determined by the LPAR time offset and the real hardware TOD). In the dark days before CP had the SET VTOD command, we used a small program that obtained the virtual machine TOD, applied the offset and then issued a SCK. As long as it does not involve a manual action, the skew can be fairly small. -Rob
