WDSC connections run a job on the System i. Its usually called QZRCSRVS
with a user of QUSER. If you haven't already done so, perhaps you could
identity the job making the connection (perhaps using a WRKOBJLCK) and then
looking for a joblog after you lose connection.

"Smith, Mike"
sources.com> To
Sent by: "Midrange Systems Technical
midrange-l-bounce Discussion"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>

03/28/2008 01:56 Subject
PM WDSC dropping connection

Please respond to
Midrange Systems

I think this is the right forum, because I don't believe the issue is
with WDSC itself, but tell me if I need to post in the WDSC forum.

I have 2 connections 1 to a production machine and 1 to a development
machine. If I connect using my profile on production and for example
open a file on the IFS. I can continue to open the file even an hour or
2 later. However, If I do the same thing on my development machine,
after about an hour I receive a TCP connection dropped message if I try
to open the file again. This happens with editing source also.

I have tried comparing system values specifically QINACTITV(60) and
QINACTMSQ(points to a specific message queue) and they are the same on
both machines. It seems like it might be a system value issue, but I
don't see anything that stands out to me as the culprit.

Anybody have an idea what will cause this?


Michael Smith

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This thread ...


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

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