On Wed, Oct 26, 2005 at 03:31:03PM -0500, McKown, John wrote: > Has anybody on the "other" side tried to use this as an argument that > z/OS is so poorly designed that it cannot stand changing the clock > without an outage? Around here, any glitch, however minor, is taken up > by the Windows zealots as yet another reason that we should totally > eliminate the zSeries. And they are winning the war.
Been there, back in the 1980s at USC. The anti-mainframe zealots (TOPS-20, VMS, and unix in those days) made that argument. So I wrote TZALT which is available here: http://ldworen.net/mvs/free-ldw.html I believe there are still some shops using it. On Wed, Oct 26, 2005 at 04:53:20PM -0500, Rob Wunderlich wrote: > I have had the Windows crowd give me funny looks when I tell them I have to > POR my box to change the GMT clock. Is that anything like having to reboot for a McAfee VirusScan update, or having to reboot for the most trivial of other software installs on Winblows? Why in the #$*& do I have to reboot for a new version of Eudora? (Don't answer that -- I've moved from Eudora to Thunderbird.) > Damm thing drifts a few seconds a month > and there are financial reasons why it can't be more than 10 seconds off > from popcorn (For those of you outside the US, popcorn is the telephone > number you dial to get the "official time"). Telephone? I set my watch from my PC clock and my PC clocks are never more than a small fraction of a second off of the atomic clock, courtesy of ntp which is standard on *ix systems like linux and easily supported on Windoze via a program that NIST distributes for free. (The built-in Winblows client just plain doesn't work reliably. What a surprise.) So the question is why can't the z boxes use ntp to stay accurate? /Leonard ---------------------------------------------------------------------- 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
