I think RDi/RDP/WDSC all have the Job Status View (my WDSC and RDi
versions do). Keep that view open in a quick view or grouped in another
region and then set the timer to an interval that is short enough for
you. This view will ping the server for the current status of the list
of jobs it keeps.
The only thing you need to do is submit a job from the tool via compile
in batch or a batch command from the commands log view.
Thanks, Matt
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Schmidt, Mihael
Sent: Tuesday, May 25, 2010 1:45 AM
To: Rational Developer for IBM i / Websphere Development Studio Client
forSystem i & iSeries
Subject: Re: [WDSCI-L] RDP Won't give up
Yes. It would be nice if RDP had an Eclipse background job which would
keep the connection to the various host servers alive (which BTW is
really simple to code,
http://rpgnextgen.svn.sourceforge.net/viewvc/rpgnextgen/src/rpgng/src/de
/rpgng/KeepConnectionJob.java?revision=22&view=markup )
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Jon Paris
Sent: Monday, May 24, 2010 8:44 PM
To: Wdsci-L
Subject: [WDSCI-L] RDP Won't give up
Has anyone found a good reliable way to get RDP to give up quickly on
connections that aren't going anywhere?
One of the systems I connect to regularly (actually two of them) time
out the remote connections - but of course RDP doesn't get notified.
So when unwittingly I try to do something it spins its wheels forever
before it will fail. Even canceling the request with the little red
button seems to have no effect most of the time. It has just done it
to me again and it took over 5 minutes for it to "notice" and issue an
error message.
By the way - this isn't a new problem - WDSC and RDi had it too. I had
hoped that when the cancel button became available it would cure the
problem but no such luck.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
midrange.com
