×
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.
On Thu, 2014-11-20 at 12:52 -0500, John R. Smith, Jr. wrote:
OK, more details.
You are correct and I apparently did not hit the C hard enough. :) I am
running WDSC - IBM Websphere Development Studio Client for iSeries version
7.0.0.
I have the same problem, using the old WDSC against the free pub1
server.
I have noticed that it usually allows a single "reconnect" (I have it
auto connect when I push a member) if it drops the connection, this
usually causes it to issue a message about "member has been changed" as
it seems to realise the connection has dropped during the push, which I
then ignore.
On a second time out it refuses to reconnect, so requires a restart of
wdsc... however it has only once complained about the member being
locked and on investigation it was due to a lock on the server job for
wdsc communication. Every other time it has not had a lock... while I
didn't investigate further I would guess that after some time the server
job realises its no longer communicating and then kills the job, hence
no lock.
Apart from during debug/multiple sucessive minor quick changes I have
changed my working methods to usually work off line, only connecting to
push and compile, then off line'ing again which might also account for
the lack of locks I have encountered.
Jon
As an Amazon Associate we earn from qualifying purchases.