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 com.ibm.as400.access.AS400.getJobs(int 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 â
Mihael
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave Shaw
Sent: Tuesday, May 25, 2010 6:28 PM
To: Rational Developer for IBM i / Websphere Development Studio Clientfor System i & iSeries
Subject: Re: [WDSCI-L] RDP Won't give up
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.
midrange.com
