Re: Source member locked - even after closing

It is released normally Roger.

The usual cause of this is when RDi gains a lock but the connection is subsequently dropped. If the lock timeout is such that you end up using RDi with that member again before the lock is dropped, RDi will be forced to get a new lock - it has to since it is a new job.

I usually use work with locks to identify the job that is hung and kill it.

It may show up under the RDi server jobs - never thought to look since I need to know which job holds the lock.

Happens to me from time to time due to being timed out on the VPN.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Mar 6, 2015, at 4:25 PM, Roger Harman <roger.harman@xxxxxxxxxxx> wrote:

In searching on this topic I found a number of comments but don't seem to find a definitive solution.

Even after closing the editor tab for a source member, job QRWTSRVR retains a lock on it. This is causing problems for me as our CMS (Turnover) cannot promote a change until the lock is released. I end up having to restart RDi to release it.

Is there a way to have the lock released when the member is closed in RDi?

Thanks.



Roger Harman

COMMON Certified Application Developer - ILE RPG on IBM i on Power



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