British Columbians are doublechecking their appointment times as the change to permanent daylight time causes confusion.Subscribe to CTV News to watch more v...
My employer’s computer system is so old …and the devs that know how to work on it are all retired… they can’t fix it with to add or adjust the new time zones. So instead of calling one of the retired guys to come contract out to fix it, like they did for a different system change they did a few years ago, they’re just going to leave it and make us all operate in a different time zone at work.
As I said in another comment, it’s a national company so we operate in several different time zones. The issue comes from the fact that Ontario and Quebec (I think) are still changing their clocks. Otherwise I’m sure they could just change the clock on whatever server is running these legacy systems.
It’s also a mainframe system so we are all logging into one system.
Also also (and I didn’t find this out until this shit show happened) our employees in Saskatchewan have already been dealing with work time vs town time for like… well forever it looks like. So maybe the system NEVER could adjust for DST and the only reason it worked was because someone is manually adjusting the clock on the server. Idk. I’m at a complete fucking loss as to why this is an issue now, let alone how this could have been an ongoing issue in Saskatchewan for DECADES without anyone figuring out how to deal with it.
The issue is that its a national operation so the difference between provinces that changed and provinces that didn’t change creates the problem.
They would either need to create new time zone profiles for the provinces ditching daylight savings or they would have to manually swap the time zones of certain locations in the system every 6 months. I gather that both are now beyond the IT department’s
ability.
They would have to figure out changing a bunch of location’s time zones though and that *may* be beyond their capability. Also I don’t know if the system has Yukon’s time zone or not since we don’t operate there.
Its starting to cause a whole ton of small issues and now some relatively minor pay issues due to this potentially allowing the company to dodge shift differential pay.
I would go into more detail on a lot of stuff but I don’t want to name the company or anything.
My employer’s computer system is so old …and the devs that know how to work on it are all retired… they can’t fix it with to add or adjust the new time zones. So instead of calling one of the retired guys to come contract out to fix it, like they did for a different system change they did a few years ago, they’re just going to leave it and make us all operate in a different time zone at work.
Just choose Saskatchewan time been around forever and has no DST. So -6 the whole year.
As I said in another comment, it’s a national company so we operate in several different time zones. The issue comes from the fact that Ontario and Quebec (I think) are still changing their clocks. Otherwise I’m sure they could just change the clock on whatever server is running these legacy systems.
It’s also a mainframe system so we are all logging into one system.
Also also (and I didn’t find this out until this shit show happened) our employees in Saskatchewan have already been dealing with work time vs town time for like… well forever it looks like. So maybe the system NEVER could adjust for DST and the only reason it worked was because someone is manually adjusting the clock on the server. Idk. I’m at a complete fucking loss as to why this is an issue now, let alone how this could have been an ongoing issue in Saskatchewan for DECADES without anyone figuring out how to deal with it.
No one knows how to adjust the time to UTC-x on an AS400?
The issue is that its a national operation so the difference between provinces that changed and provinces that didn’t change creates the problem.
They would either need to create new time zone profiles for the provinces ditching daylight savings or they would have to manually swap the time zones of certain locations in the system every 6 months. I gather that both are now beyond the IT department’s ability.
Yukon time exists and it’s a perfect interim match.
They would have to figure out changing a bunch of location’s time zones though and that *may* be beyond their capability. Also I don’t know if the system has Yukon’s time zone or not since we don’t operate there.
Its starting to cause a whole ton of small issues and now some relatively minor pay issues due to this potentially allowing the company to dodge shift differential pay.
I would go into more detail on a lot of stuff but I don’t want to name the company or anything.