I have checked with development and this would be a candidate for an RFE
Currently, when the user tries to save in the new RDP session, we compare
the last-updated timestamp and put up the 'Save Conflict' dialog prompting
them what to do.
We could explore the possibility of adding function to check the host
timestamp when RDP is started (or if they type changes in the file ? or
bring the file edit session into focus ... ) and then either put a new lock
on the file, or go into the Save Conflict prompt ... ( or a modified
version of it)
Might even be cool to offer a new option to show them the differences
between theirs and host version .. them let them decide ...
To ignore the cache and always open from the host would slow down the
reopening of RDp considerably by having to download all the files, also the
developer would not be made aware of any changes made since the last time
they edited. The solution above would defer the cost of communication
until it was necessary.
Regards,
Edmund (E.H.) Reinhardt
COBOL IDE on AIX, DDS, WebFacing, System i Application Development,
Rational Developer for Power
2D barcode - Phone: 1-905-413-3125 | Phone: 1-905-854-6195 IBM
encoded with E-mail: edmund.reinhardt@xxxxxxxxxx
contact AIX COBOL: 8200 Warden Ave
information www.youtube.com/user/IBMRational#g/c/62DF24D5BCD43501 Markham, ON L6G 1C7
"In every thing give thanks: for this is the will of Canada
God in Christ Jesus concerning you." - 1
Thessalonians 5:18
From: Kurt Anderson <kurt.anderson@xxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
<wdsci-l@xxxxxxxxxxxx>
Date: 07/28/2011 03:33 PM
Subject: Re: [WDSCI-L] Refresh the member lock
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
Why can't RDp initiate the open member logic and retrieve the source from
the library it resides in instead of opening a local copy of the source?
Wouldn't that alleviate any problems with locking?
-Kurt
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Ron
Sent: Thursday, July 28, 2011 1:48 PM
To: 'Rational Developer for IBM i / Websphere Development Studio Clientfor
System i & iSeries'
Subject: Re: [WDSCI-L] Refresh the member lock
I think the preference that is being referred to only applies to the remote
system view and not how individual source members are treated. Basically if
you leave a member open when you close RDP then you'll be working with a
local copy when you restart and a remote lock will not be in place. When
RDP is shutdown cleanly all remote jobs, and therefore locks, are
terminated.
After you restart the source member will not be flagged as changed but
after you makes changes and save the source member a new remote connection
will be made. If there are differences on the remote system RDP will tell
you if the member has been changed.
I also agreed with the comment that you need some type of change management
in place with check out into separate development libraries to effectively
control your development work.
Ron
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of MichaelQuigley@xxxxxxxxxx
Sent: Thursday, July 28, 2011 1:20 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Refresh the member lock
wdsci-l-bounces@xxxxxxxxxxxx wrote on 07/28/2011 01:00:08 PM:
----- Message from "DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx> on Thu,
28 Jul 2011 14:19:55 +0000 -----
To:
Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject:
Re: [WDSCI-L] Refresh the member lock
There's a property in
Preferences > Remote Systems >> Use Cached information to restore the
remote view
I have seen the behavior you describe when this property is checked,
and I closed Rdi without closing the LPEX editors. When the IDE is
re-launched, the LPEX sessions open from the cached source, without
even trying to lock the host member. I always uncheck this property.
Hth,
-Eric DeLong
Eric,
In RDP, do you have to reopen the source members or does the workbench open
them from the host? In WDSc the member is reopened, but it still is from
locally cached source.
Thanks,
Michael
--
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.
--
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.
--
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
