It doesn't matter what job you monitor. In fact, the job I'm monitoring for one of my connections doesn't actually exist on the machine anymore, as it was ended from the job queue. The point is that the refresh causes activity over the connection, so the connection job doesn't time out and end. Remember, there's a job in QUSRWRK for each open connection - the problem is that inactive job timers on the i can end that job, thereby closing the connection without WDSCi/RDi/RDP knowing the connection's gone. Have that connection job do something every 20 or 30 minutes and it won't end.

Dave Shaw
Mohawk Industries


----- Original Message ----- From: "Schmidt, Mihael" <Mihael.Schmidt@xxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio Client forSystem i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Sent: Tuesday, May 25, 2010 10:28 AM
Subject: Re: [WDSCI-L] RDP Won't give up


I don't think that this will work. There are different jobs depending on work they should do. So just using the view might keep the command job active but may let the file or RLA job timeout, depending on implementation.


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