Hi Peter,
I believe that this issue will be resolved for the next update to the
product, there is an internal APAR SE53956 open for it.
You can avoid the issue by being careful to not open files when refreshing
the outline. As you might guess the problem is made worse by opening a
bunch of files at the same time when using the live outline. Moving to
the old static outline view may also mitigate it to some extent as that
makes it less likely that the outline is refreshing when a new member is
being loaded into the editor.
If you see the problem then closing the open members and clearing the
cache may be a good idea ;)
Mike
Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199
From: Peter Thomas <Peter.Thomas@xxxxxxxxxx>
To: "WDSCI-L@xxxxxxxxxxxx" <WDSCI-L@xxxxxxxxxxxx>,
Date: 2013-03-06 22:47
Subject: [WDSCI-L] Latest member source changes not being retrieved
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
_______________________________________________________________________________________
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.
_______________________________________________________________________________________
midrange.com
