The host server jobs don't time out on my systems. The only job that gets killed by the inactivity timers is the connection job. Having the job status display refresh every 30 minutes resets the inactivity timers, so the connection job stays up.

Besides, you can argue about whether it should work all you want - I've tried it, and it solves my specific problem, which I believe is the same problem Jon stated originally. Granted it's a work-around and not ideal, but it's better than having to reconnect 2 or 3 times a day.

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: Wednesday, May 26, 2010 3:30 AM
Subject: Re: [WDSCI-L] RDP Won't give up

And that is the point where I think that you are wrong. There is more than one job for a connection. Why do you think there are multiple host servers running for receiving the different connection requests?

My assumption is also based on the fact that you have to specify the service type on the API type) like

AS400 system = new AS400();
Job[] jobs = system.getJobs(AS400.COMMAND);

The API even supports multiple jobs for the same service type so you might even have to "ping" all jobs (though I never encountered more than one job).

My 0.02 â

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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