I had a similar issue with a new change management tracking system, opening a 
ticket for time change, well duh, the change was to occur for us @ 02:00 
Central time, entering that time was invalid, I wanted to stick by the rules :) 
and select the actual time, fortunately the technical services person for the 
product working with us was on site and I told him of my issue, he suggested I 
use 01:59 or 02:01 at an actual start time, OK, 
so once saved the actual start time was altered to 03:01 - 
Working for Boeing some time ago - the 777 project was ramping up and we had 
engineers all over the globe working on CATIA models, the system selected to 
keep track of all the models was DB2, it was at that time Boeing decided to use 
GMT and no longer use local time, lots of work, lots of changes to get there, 
but there was not confusion on what time a model was updated and by whom. 



Carmen Vitullo 

----- Original Message -----

From: "Paul Gilmartin" <[email protected]> 
To: [email protected] 
Sent: Thursday, November 8, 2018 1:55:54 PM 
Subject: Re: Speaking of time change... 

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 


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to