We were arguing (discussing) today at the office, whether or not Pro/Intralink will hick-up for the upcoming DST change in the USA. Our I.T. guy said there is no patch available for our Win2000 machines, only XP and Win2003. We're not sure if it will effect the revision / version status of Intralink objects. Some said that Intralink only stores according to revision / version and doesn't really care about date / time. I mean really... What is the likelihood of someone else and myself both checking an existing (modified) object with the same name, at exactly the same date and time HH:MM:SS - pretty small I guess.
Has anyone come up with a concise plan regarding the upcoming DST change and Pro/E Wildfire and Pro/Intralink? Is this worth worrying about, or not?
The information contained in this electronic mail message is privileged and confidential information, may be subject to the attorney-client privilege and is intended solely for the use of the addressee. If you are not the intended recipient, any disclosure, copying, distribution, or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message in error, please notify me immediately.
DST - Have there been any resolutions yet?According to the TPI last week:
PLEASE NOTE: Pro/INTRALINK 3.x customers should rest assured this is not a repeat of the previous Pro/INTRALINK 3.x Daylight Saving Time issue as documented in Solution 113911 (located at: http://www.ptc.com/appserver/cs/view/solution.jsp?n=113911). Objects will NOT be marked as modified in the Workspace.
What is conceivable is that your timestamps will be off by one hour for a three week period in March.
You do need to execute the tzupdater.jar file on your Pro/INTRALINK client JRE installation by running something similiar to the following command: C:\ptc\ilink\i486_nt\jre\bin\java.exe -jar C:\tzupdater.jar -u -v The tzupdater.jar file is available via Sun's website at