Re: Timeout Errors

Youi are correct, it should behave as you desire after the change.

That said, since that parameter takes immediate (nor nearly) effect, you can
change it back if the results are not as you had hoped.


--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Tuesday, June 05, 2018 8:17 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Timeout Errors

Thanks Jim!

So, in essence, no harm, no foul by changing the TCPKEEPALV from 1000 to 15?
I apologize if I'm not picking up the obvious from your response, but I want
to make sure I don't introduce problems for already stressed out developers
and testers.

- Dan

On Tue, Jun 5, 2018 at 8:05 AM, Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx

wrote:

More likely than not wanting any keep alive the person making the
change (or asking for it if it was the boss/auditor) did not
understand the ramifications of that specific setting.

We see that all the time, particularly with the weighting on an
uncapped partition definition. That's not a priority, its weighting
and it behaves differently than some folks think.

--
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: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/wdsci-l.