Daylight Savings Time Rant 4

[Nortel4Ever]

Can anyone tell me why a 30 year old Norstar is smart enough to be able to turn on Daylight Savings Time at 02:00 on the second Sunday of March, and turn it off at 02:00 on the first Sunday of November regardless of the year, but the IPO requires specific yearly entries in Manager to be able to do the same thing? Entries that expire at some point and have to me manually updated.

I'm talking about ubiquitous small IPOs with Embedded VM and the time source either set to None or SNTP. Even with SNTP in use and working DST entries are required to perform the time adjustment.

...and you think Avaya could have made the process of manually inputting DST entries into Manager somewhat simple, but noooo, it's tedious has hell!!!

 

[Westi]

Hi Nortel4Ever
ridiculous comes to mind but hey they get away with it.

To update the times you can change the time zone, save it, open a config again and change it back.
No reboot and it will add 2 more years to the schedule automatically.

Of course I had a 8.0.66 system that did not for anything in the world add that and I just set it to use Manager as time source.
Avaya - 10 systems all programmed the same do different things if they want to.

Joe
FHandw, ACSS, ACIS

"Dew knot truss yore Spell Cheque

 

[sizbut]

Because that rule only applies for North America (and even then not in Arizona). And the rules changed in 1986, and changed again in 2007, and may not even apply in 2023.

And then there's the rest of the world...

Stuck in a never ending cycle of file copying.

 

[Nortel4Ever]

... still, for a 30 year old KSU with auto-DST that could be enabled or disabled based upon locale, and updated software as of 2007, to be able to adjust based solely on day and month without the need for specific yearly entries is impressive. There is no reason Avaya couldn't have done the same thing.

 

[biv343]

I'll have to try what Westi said, and have a star Westi for the idea.

To update the times you can change the time zone, save it, open a config again and change it back.
No reboot and it will add 2 more years to the schedule automatically.

I didn't know that was possible and never tried that. I've gone the old school route of deleting old entries from the top of the list and adding new ones. That isn't hard, just time consuming.

Out of all the systems I work on, I've had three with DST issues this week, and every one has been something different.

 

[critchey]

I just had a customer still running a R7 system call in wanting to add a SNTP server and his DST entries only went till 2021. Before I found this post I had him try entering a time server, save, remove, save, reopen manager and it did not add DST entries. Westi's solution of changing time zone and going through this did work even on this older system.

The truth is just an excuse for lack of imagination.

 

[Nortel4Ever]

This did work for me, but I had to delete a couple of old entries first to make room for new ones, change the time zone as above, Merge, change it back, Merge, and bada boom, bada bing there were 2 new entries. It didn't seem to matter how many old entries I deleted first as Manager would only add 2, for 2022 and 2023.