Last time I checked (15 seconds ago), that's exactly what RDp doesn't do. ;)
Seriously. I have a source open for edit in RDp. I closed it. I re-opened RDp, which also opened the source. I went into SEU and go into that source in edit mode. RDp does not have the lock as might be suggested when having the source open in RDp in edit mode.
For the record, I'm in agreement with Justin. Seems to me that people are trying to make this more convoluted an issue than it is.
-Kurt
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Friday, July 29, 2011 3:40 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] Refresh the member lock
On 7/29/2011 3:19 PM, Justin Taylor wrote:
IMO, it seems to me to be a simple problem, with an equally simple
solution. RDp is re-opening source members without locking them.
RDp needs to be fixed to relock those source members or open the
member in browse if it cannot get a lock (notifying the user of
course).
Last time I checked (which is about 30 seconds ago), that's exactly what RDp does.
If a member is locked by another editor, it displays a dialog indicating that the member is locked and tells you what job is holding the lock.
You're offered the ability to open the member in browse mode or end the other job and open the member in edit mode (assuming, of course, you have the authority to end the other job).
david
--
IBM i on Power - For when you can't afford to be out of business
--
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
