Peter,
this problem occured also to me. And it occurred also to several customers
of us. And I found several threads in different forums of people with the
same problem. The problem at us was that it was not reproducible. I opened a
service request at IBM but because it was not reproducible they couldn`t
help us.
If you open a service request they probably recommend you to clear the cache
via the preferences and disable the caching function. But in my opinion this
can`t be the solution.
One of our customers has written a batch script which deletes all temporary
files in the cache in folder RemoteSystemsTempFiles in the workspace every
time prior they start RDP. But it think this also can`t be the solution.
It is definitely a cache problem and it is definitely a bug. Hopefully IBM
find a solution soon and provide a fix.
Frank
-----Ursprüngliche Nachricht-----
Von: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im
Auftrag von Peter Thomas
Gesendet: Donnerstag, 7. März 2013 04:47
An: WDSCI-L@xxxxxxxxxxxx
Betreff: [WDSCI-L] Latest member source changes not being retrieved
____________________________________________________________________________
___________
Note: This e-mail is subject to the disclaimer contained at the bottom of
this message.
____________________________________________________________________________
___________
I wonder if anyone has experienced the following behaviour.
One of my colleagues has recently started using RDP 8.5. He discovered that
he wasn't retrieving the latest changes people had applied using SEU.
I tested this myself on his PC and even though I was using Ctl Shift A it
did not retrieve the latest change I had just made using SEU.
I even opened the member in RDP and then tried to open it at the same time
in SEU. It gave me a member locked error. The same happened if I did the
opposite.
Opened it in SEU for edit and then tried to open it in RDP. It gave me a
member locked error.
However if I made a small change in SEU and then saved it. Then opened it in
RDP, the change was not visible.
I then noticed that the connection he was using was a previous alias of the
machine name. I changed the connection to use the current name and
everything started to work OK.
When I pinged the alias name and the current name the return IP address and
name were the same.
I can't explain what was causing the problem. It seemed to be keeping a
local copy of the changes.
Peter
____________________________________________________________________________
___________
The information transmitted in this message and its attachments (if any) is
intended only for the person or entity to which it is addressed.
The message may contain confidential and/or privileged material. Any review,
retransmission, dissemination or other use of, or taking of any action in
reliance upon this information, by persons or entities other than the
intended recipient is prohibited.
If you have received this in error, please contact the sender and delete
this e-mail and associated material from any computer.
The intended recipient of this e-mail may only use, reproduce, disclose or
distribute the information contained in this e-mail and any attached files,
with the permission of the sender.
This message has been scanned for viruses.
____________________________________________________________________________
___________
--
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.
midrange.com
