On Wed, 7 Nov 2018 17:12:47 -0800, Charles Mills wrote: >Should be called "Why Doctors Should Hate Local Time." > So many things to go wrong.
Late one week a while ago, I got an E-invitation to a meeting early the next week which showed both local time and GMT. They disagreed by one hour, probably because of an intervening DST boundary. I tracked the problem up the chain and opened an SR with company IT. They said the GMT was added automatically by a Microsoft scheduling app and that Microsoft was aware of the behavior and deemed it WAD. A peer once reported an unresolvable DWIM. His mobile device automatically adjusts its time display for time zone (GPS?) But he wants some events such as the daily wakeup alarm to happen at 0600, local, whatever timezone he happens to be in. But others, such as the recurrent conference call to corporate HQ, to happen at the same GMT, regardless. The device provides no way to control this. In the early days of MVS (pre-z) UNIX System Services, I set the TZ environment variable for my session and tried a C compilation. Dismayingly, the __TIME__ and __DATE__ macros and the listing page headers showed the system time, not the values in the TZ I had set. PMR. "WAD". But, magically, the problem quietly vanished in a subsequent release. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
