Well, I updated all my Win servers, all our PC's, and the iSeries, and still got caught by the darn DST thing.
Seems the iSeries created a new time zone, that moved the DST effective dates for 2007 and beyond. However, MS patch did not. Instead, it patched the current time zone, meaning it affected these 4 weeks retroactively for past years.
So, who cares ? Well. we have IFS files that download to local clients (250MB) whenever the time stamp changes. Normally very little changes as we do new releases. However, move than 70% of these files had timestamps in the 3/10/2006 to 3/30/2006 time range (initial release). Now MS machines have adjusted the timestamps by 1 hour, but the iSeries did not.
So now, all the clients are getting about 200MB downloads. For local users this isn't really a big deal, but remotes will take 3 - 10 hours each.
Thanks M$. Infor XA users will probably all get hit by this.
Seems the iSeries created a new time zone, that moved the DST effective dates for 2007 and beyond. However, MS patch did not. Instead, it patched the current time zone, meaning it affected these 4 weeks retroactively for past years.
So, who cares ? Well. we have IFS files that download to local clients (250MB) whenever the time stamp changes. Normally very little changes as we do new releases. However, move than 70% of these files had timestamps in the 3/10/2006 to 3/30/2006 time range (initial release). Now MS machines have adjusted the timestamps by 1 hour, but the iSeries did not.
So now, all the clients are getting about 200MB downloads. For local users this isn't really a big deal, but remotes will take 3 - 10 hours each.
Thanks M$. Infor XA users will probably all get hit by this.
Comment