You cannot set the real HW clock on a 390 from Linux (or any other OS) without human intervention at the physical processor console to enable access to the clock hardware. The hardware is designed to work that way, and Linux can't change it.
Linux gets it's initial date from the HW clock at boot and never consults it again. For the reason listed above, trying to store a value to the HW clock isn't really very useful, and there's no point in trying. Use date or NTP. If you have more than one system, you should be using NTP anyway to synchronize them all to the same time and keep them that way. NTP constantly adjusts the time on all participating machines so that all machines are within a small delta of the same time. This is important for lots of authentication stuff. -- db David Boyes Sine Nomine Associates > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Leonardo Rodriguez > Sent: Friday, January 16, 2004 4:04 PM > To: [EMAIL PROTECTED] > Subject: Re: Setting Clock Time > > > The problem with the date command is that I have read that > this command > doesn't store > the values at boot moment but the hwclock command does, is it true?
