There are two ways of editing source in RDP/WDSC/etc.: Connected and disconnected. One of the selling points I saw some time back was that you could edit and verify your source disconnected from the server and then upload it at your convenience when a connection becomes available.
With this in mind, the timestamp checking is probably to work out whether the change dates on the source member are older than those on the locally cached member. If so, load the cached version.
If this is the way it works, then it would probably be a good idea to remove the cached version everytime the source member is uploaded to the server to prevent corruptions in update timestamps. There may be an RFE in this to prevent possible problems and to keep the local workspace trim and healthy, but someone from IBM would need to weigh in first just in case everything I am guessing about is complete rubbish and Thierry's guess at a pointless timestamp check is more correct.
-Paul.
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Thierry Bernard
Sent: 04 July 2012 02:47
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDP 8.5 Open Service Requests
We had this issue on 8.0.0.3 and I opened a SR, saying how scary the issue was.
One problem is that this issue is not readily reproducible.
If I remember correctly, the server was sometimes sending an incorrect timestamp. There had a test fix for after 8.0.3.1 but as I was not able to reproduce, I did not try it. Presumably, that fix is included in 8.5.
From your findings, it seems it does not fully solve the issue.
During the SR back and forth, I tried unsuccessfully to convince them that given the severity of the consequences when the issue arises (lost source changes), they should not even be checking timestamps when opening a member. It's called REMOTE System Explorer, after all, so open the remote member. (Or maybe have it as an option for those that work on slower connections.) I still think it's the only safe way to open the current member on the server. If you agree and add your voice, now that is has been shown the fix does not work, maybe they'll change their mind and do it...
Thank you and have a nice day.
Thierry.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
Scanned by MailDefender - managed email security from intY - www.maildefender.net
Important
This email transmission and any files with it are strictly
confidential to the intended recipient and may be legally
privileged. Any views or opinions presented are solely
those of the author and do not necessarily represent those
of BHSF. If you are not the intended recipient, you must
not copy, disclose or distribute its contents in any way.
If you have received this e-mail in error, please notify
the sender and delete the e-mail from your system.
We have taken steps to ensure this e-mail and attachments
are free from any virus but do not accept any
responsibility once this e-mail has been transmitted. You
should scan any attachments for viruses.
No contract may be concluded on behalf of BHSF Limited by
e-mail.
Registered Office:
BHSF Limited
Gamgee House, 2 Darnley Road, Birmingham B16 8TE.
www.bhsf.co.uk
Registered in England number 35500.
BHSF is authorised and regulated by the Financial Services
Authority.
midrange.com
