Robert,
YMMV on this, as whether it works seems to depend on a bunch of different
things, not all of which I've figured out. It helped an issue I was having at
V5R4 that seemed to go away at 6.1, but doesn't usually help another issue I
have when working remotely over a Cisco VPN.
The navigation steps I'm giving are for WDSCi 7.0 in US English, which is all I
have. I don't know if IBM has made any changes in later releases, or what it
looks like in other languages.
To open the Job Status view:
Window => Show View => Other, then expand iSeries (they probably renamed this at
some point), then select iSeries Job Status (again, probably renamed in later
releases). Once it's open, I make it a Fast View. You adjust the refresh
interval using the slider across the bottom.
To get a job in the list if you don't have any:
Window => Preferences, then filter for Command. There should be a Command
Execution page under Remote Systems, iSeries (or whatever). Make sure 'Add
batch commands to the iSeries Job Status view' is checked, then OK.
Open the Command Log for the connection you want to keep open and submit a batch
command (use the pull down next to Command to specify Batch) to run something
innocuous (I like dsplibl output(*print). A job will submit and will appear in
the Job Status view.
If you set the refresh interval to a good value and if the planets align, this
view will ping the server for a status update on the job(s) in the list often
enough to keep the connection open. If you're using a different connection than
it is, or if any of a number of things happens, it doesn't work. Good luck with
it! I hope it helps you. Also, don't let too many jobs build up in this view,
as the more you have, the more resources it requires on your PC and the server
each time it refreshes.
Dave Shaw
----- Original Message ----
From: Robert Rogerson <rrogerson@xxxxxxxxxxx>
To: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
Sent: Mon, June 3, 2013 11:14:52 AM
Subject: [WDSCI-L] Connection Timeouts...
In the archives
([1]
http://archive.midrange.com/wdsci-l/201005/msg00137.html) Dave Shaw
mentions "Having the job status display refresh every 30 minutes resets
the inactivity timers, so the connection job stays up."
Can Dave or someone explain how I would do this so I can give it a try and
see if fixes my connections dropping.
midrange.com
