The open member logic you refer too is initiated when you save the RDP copy
of the source member. That could probably happen automatically when you
started RDP but the problems you would face would be no different (which
source member version is right, how do I synch them up) then dealing with it
when you save. RDP is actually pretty smart in that it tells you the source
member on the remote system is different. I don't see this as being any
different then, say, opening the same text file on your PC with two
instances of notepad. One of those instances is going to be the one that
determines the final contents of the text file.
There is also the whole issue of wanting to work offline so its
understandable why RDP is designed the way it is. There have been many times
when working offline for days and then refreshing the "master" copy has been
very helpful. I don't see how IBM could effectively maintain a lock on the
master during this time of offline maintenance.
By far the easiest way to deal with this is not to leave any members opened
when you close RDP. I don't think there is a setting for that but its as
easy as doing a File|Close All (Ctrl+Shift+W) before you exit.
Ron
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Kurt Anderson
Sent: Thursday, July 28, 2011 2:27 PM
To: Rational Developer for IBM i / Websphere Development Studio Client
forSystem i & iSeries
Subject: Re: [WDSCI-L] Refresh the member lock
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
