In a recent note, Edward Jaffe said: > Date: Thu, 11 May 2006 12:35:10 -0700 > > McKown, John wrote: > >> Ed Jaffe wrote: > >> > >> Issue a daily SET TIMEZONE= command to adjust the local time > >> as necessary. > >> > > Well, we are planning on doing a T CLOCK=. In what way would a T > > TIMEZONE= be better? Oh, and just to myself, I don't really like this > > too very much. But then, I'm just an old grump. > > SET TIMEZONE is superior to SET CLOCK because the amount of time > required to process the command is not a factor. > Errr... But doesn't that still leave the GMT incorrect? Dammit, GMT matters. In some senses it matters more than local time, since critical timestamps are kept (by IBM's recommendation) in GMT.
OTOH, I've wondered (even here, with no followup) about the relative merit of zapping (Key-0, Compare Double and SWAP) CVTLSO. This would get both local and GMT correct. Just everyone wait for STP. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
