1 Aug 2011 10:43
Re: Refresh the member lock
As far as I can see, the source member lock does one thing only. It prevents two SEU developers having the source open for edit at the same time. That is, only one developer can edit the source using SEU at a time. If your session closes/crashes or just SEU closes unexpectedly then your source member lock will be re-established the next time you open it in SEU. If the source is open in RDP and it was loaded from an IBM i connection for editing then that source member should always be locked whenever my RDP session is active. This is what happens with SEU, so why not RDP? Currently, after restarting RDP (after it was closed/crashed with a source member open) it appears to have opened the source member again, but no locks or source changed checks are done until you try to save your changes again. So I think RDP should re-establish the member lock as soon as the source member becomes changed (or "dirty" as it used to be called) simulating reopening the source in SEU. Maybe an option to work offline should be available somewhere, so people who do edit without a permanent connection to their IBM i can continue to work as they do (e.g. using i Projects), but the option should not be on by default for source members loaded via an IBM i connection. Kurt, did you raise the RFE? I could do it myself, I think, but it would take extra time for me to do it while I worked out *how* to do it. -Paul. -----Original Message----- From: wdsci-l-bounces@... [mailto:wdsci-l-bounces@...] On Behalf Of Kurt Anderson Sent: 29 July 2011 22:24 To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries Subject: Re: [WDSCI-L] Refresh the member lock Last time I checked (15 seconds ago), that's exactly what RDp doesn't do. ;)(Continue reading)
RSS Feed