× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Another solution might be to work in separate developer libraries for each
programmer -- then no one else would be trying to edit your members in the
first place.

Stu


On Thu, Jul 28, 2011 at 09:19, DeLong, Eric <EDeLong@xxxxxxxxxxxxxxx> wrote:

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

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Ron
Sent: Thursday, July 28, 2011 8:59 AM
To: 'Rational Developer for IBM i / Websphere Development Studio Clientfor
System i & iSeries'
Subject: Re: [WDSCI-L] Refresh the member lock


The probable issue here is that when the source member is opened the second
time you are actually only opening the one that was stored in your PC's
local cache. Perhaps you are opening it using the recent files list? You
need to open it from the remote systems dialogue. There might also be a
setting that determines the preference of what you open but I'm not sure.


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On
Behalf Of Paul Bailey
Sent: Thursday, July 28, 2011 3:13 AM
To: WDSCI-L@xxxxxxxxxxxx
Subject: [WDSCI-L] Refresh the member lock

Hi,

When you open a source member in RDP a lock is created on the system i so
that any SEU programmers can not open the source member for editing. This
is
all good. If you have a source member open, but close RDP and reopen RDP
later then the lock is not restored and the source member can be edited by
you in RDP but also it can be edited by someone in SEU. Obviously we then
end up with a comical farce where two programmers are racing to get their
changes saved first (or is that just me?)

I know this is an old issue, and I was hoping it would have been fixed
since
WDSC versions (I am using v8.0.0.3). Does anyone know of a workaround to
re-establish the lock on the source member before I start editing the
source
member after a restart?

The only two workarounds I can think of (as used by me in the early days)
is
to make certain all source members are automatically closed when RDP closes
(there is a preference, but I can't find it) or to manually close and
re-open the source members after I restart RDP. Any other suggestions?


Cheers,
Paul.


------------------------------------------------------------
Important

This email transmission and any files with it are strictly confidential to
the intended recipient and may be legally privileged. Any views or opinions
presented are solely those of the author and do not necessarily represent
those of BHSF. If you are not the intended recipient, you must not copy,
disclose or distribute its contents in any way.
If you have received this e-mail in error, please notify the sender and
delete the e-mail from your system.

We have taken steps to ensure this e-mail and attachments are free from any
virus but do not accept any responsibility once this e-mail has been
transmitted. You should scan any attachments for viruses.

No contract may be concluded on behalf of BHSF Limited by e-mail.

Registered Office:
BHSF Limited
Gamgee House, 2 Darnley Road, Birmingham B16 8TE.

www.bhsf.co.uk

Registered in England number 35500.

BHSF is authorised and regulated by the Financial Services Authority.


--
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.