Hi Rob,
Unfortunately RDP really does not do anything to influence the inactivity
timers. You may wish to research how to change it for the OS that you are
running RDP on. For Windows there are some registry settings that control
it and I am sure there is some way to influence it in Linux as well. It
could also be something that your VPN connection, client or remote server,
may be imposing on idle connections. In my case I can connect to an IBM i
over a VPN connection using the Cisco client and it stays connected as
long as the connection is good.
I don't know if running a Wireshark trace or similar might show you who is
closing the connection or not - I'm not a TCP/IP expert, sorry.
Mike
Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199
From: Robert Rogerson <rogersonra@xxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxx>,
Date: 2013-02-14 17:25
Subject: Re: [WDSCI-L] Empty RSEXXXXX members...
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
I'm sure the issue is that the network connection is dropping and
leaving
the member. I work remotely and I don't want to push them to resolve
my
network issue as I can easily work around it.
But if anyone does have any advise for resolving my networking issue
(the
connection drops after about 10 minutes of inactivity) I'd greatly
appreciate it. Or even if someone can suggest where to look.
Thanks,
Rob
On 2013-02-14 4:44 PM, Anderson, Kurt wrote:
In my case they did exist. Refreshing didn't help. Simply empty members
orphaned on the system. I'm guessing that's Rob's case too since he
deleted them in SEU.
-Kurt
-----Original Message-----
From: [1]wdsci-l-bounces@xxxxxxxxxxxx [[2]
mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Hockings
Sent: Thursday, February 14, 2013 2:34 PM
To: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries
Subject: Re: [WDSCI-L] Empty RSEXXXXX members...
Refresh the RSE view. I suspect that they don't really exist when you
see them (typically after starting RDP) and are a remnant of the two-stage
write that is used when writing files to the IBM i.
IIRC the underlying problem was fixed in 8.0.3 or 8.0.3.1 but I suspect
that the symptoms could occur if you have a wonky (technical term there)
network connection, wireless maybe?
Mike
Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support IBM Canada Ltd. Laboratory [3]hockings@xxxxxxxxxx voice
1-905-413-3199 T/L 313-3199 ITN 23133199
From: Robert Rogerson [4]<rogersonra@xxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client
for System i & iSeries [5]<wdsci-l@xxxxxxxxxxxx>,
Date: 2013-02-14 15:28
Subject: Re: [WDSCI-L] Empty RSEXXXXX members...
Sent by: [6]wdsci-l-bounces@xxxxxxxxxxxx
I have the same problem. But they are actually empty members in the
file
(for example QRPGLESRC) so refreshing the cache would not work. I
seem to
recall Jon Paris raising this issue a while ago but I couldn't find
the
thread in the archives.
I still use SEU for some quick fixes and if I see these members I just
delete them.
Rob
On 2013-02-14 1:51 PM, Mike Hockings wrote:
For the RSE* members maybe just try refreshing the RSE view? Clearing
the cache might also be of benefit. What version and fixpack of RDP are
you running?
Mike
Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support IBM Canada Ltd. Laboratory [[7]1]hockings@xxxxxxxxxx voice
1-905-413-3199 T/L 313-3199 ITN 23133199
From: Ken Killian [2][8]<kkillian@xxxxxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" [3][9]<wdsci-l@xxxxxxxxxxxx>,
Date: 2013-02-14 12:25
Subject: [WDSCI-L] Empty RSEXXXXX members...
Sent by: [[10]4]wdsci-l-bounces@xxxxxxxxxxxx
Hi,
Once in a while, I get EMPTY members that appear in my source file like
this:
RSE1343942
RSE1793517
RSE3718306
RSE4062168
RSE8271212
RSE8803845
They are empty, and I just delete them. These happen to appear in my
QRPGLESRC...
It appears that sometimes RDP gets a lock on my source, and I click the
check-box to "End-job" and reload...
I will try to capture the Message-box next it appears...
Oh well, I just delete these empty members...
-Ken Killian-
(423) 510-3129
References
Visible links
1. [11]mailto:hockings@xxxxxxxxxx
2. [12]mailto:kkillian@xxxxxxxxxxxx
3. [13]mailto:wdsci-l@xxxxxxxxxxxx
4. [14]mailto:wdsci-l-bounces@xxxxxxxxxxxx
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: [15]WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: [16]
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: [17]WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at [18]
http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: [19]WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: [20]
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: [21]WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at [22]
http://archive.midrange.com/wdsci-l.
References
Visible links
1. mailto:wdsci-l-bounces@xxxxxxxxxxxx
2. mailto:wdsci-l-bounces@xxxxxxxxxxxx
3. mailto:hockings@xxxxxxxxxx
4. mailto:rogersonra@xxxxxxxxx
5. mailto:wdsci-l@xxxxxxxxxxxx
6. mailto:wdsci-l-bounces@xxxxxxxxxxxx
7. mailto:1]hockings@xxxxxxxxxx
8. mailto:kkillian@xxxxxxxxxxxx
9. mailto:wdsci-l@xxxxxxxxxxxx
10. mailto:4]wdsci-l-bounces@xxxxxxxxxxxx
11. mailto:hockings@xxxxxxxxxx
12. mailto:kkillian@xxxxxxxxxxxx
13. mailto:wdsci-l@xxxxxxxxxxxx
14. mailto:wdsci-l-bounces@xxxxxxxxxxxx
15. mailto:WDSCI-L@xxxxxxxxxxxx
16.
http://lists.midrange.com/mailman/listinfo/wdsci-l
17. mailto:WDSCI-L-request@xxxxxxxxxxxx
18.
http://archive.midrange.com/wdsci-l
19. mailto:WDSCI-L@xxxxxxxxxxxx
20.
http://lists.midrange.com/mailman/listinfo/wdsci-l
21. mailto:WDSCI-L-request@xxxxxxxxxxxx
22.
http://archive.midrange.com/wdsci-l
midrange.com
