Re: Source member locked - even after closing -- WDSCI-L

Subject: Re: Source member locked - even after closing
From: MichaelQuigley@xxxxxxxxxx
Date: Mon, 9 Mar 2015 13:48:16 -0400
List-archive: <http://archive.midrange.com/wdsci-l/>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 03/07/2015 01:00:03 PM:

----- Message from Jon Paris <jon.paris@xxxxxxxxxxxxxx> on Fri, 6
Mar 2015 17:28:27 -0500 -----

To:

Wdsci-L <wdsci-l@xxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] Source member locked - even after closing

Even local I’ll lat you odds that is the cause Roger. Inactivity
timeout or something.

A simple work with locks will show you which job has it and if it is
an RDi server job just kill it.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

Have I lost my mind? (I mean specifically in reference to this thread.) I
would swear I've released the lock by simply disconnecting and
reconnecting.

This mailing list archive is Copyright 1997-2026 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.