SESTIMEOUT parameter
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
SESTIMEOUT parameter

 
Post new topic   Reply to topic    Windows Server Forum Index -> Host Integration Server
Author Message
Pinar
Guest
Posted: Mon Sep 19, 2005 4:52 pm    Post subject: SESTIMEOUT parameter Reply with quote
Hello,
We are using LU 6.2 sessions to access/run maniframe transactions. I
increased SESTIMEOUT registry parameter from 20 sec to 4 minute on HIS
server. So LU6.2 sessions will be kept open during 4 minute. Thus, HIS
server will try to use
existing sessions first. But after that change, number of sessions increased
on HIS server.
Why HIS server needs to open a new session evenif it has alreay free
one?What is the criterion of opening LU62 session?
What is the optimum value of SESTIMEOUT parameter? Is 4 minute right for us?
How can I determine correct value?

Thanks .
Pinar Erdim
Yapi Kredi Bank
Back to top
Neil Pike
Guest
Posted: Mon Sep 19, 2005 8:51 pm    Post subject: Re: SESTIMEOUT parameter Reply with quote
Pinar,

How many auto-activated LU6.2 sessions do you have?

Quote:
We are using LU 6.2 sessions to access/run maniframe transactions. I
increased SESTIMEOUT registry parameter from 20 sec to 4 minute on HIS
server. So LU6.2 sessions will be kept open during 4 minute. Thus, HIS
server will try to use
existing sessions first. But after that change, number of sessions increased
on HIS server.
Why HIS server needs to open a new session evenif it has alreay free
one?What is the criterion of opening LU62 session?
What is the optimum value of SESTIMEOUT parameter? Is 4 minute right for us?
How can I determine correct value?

Thanks .
Pinar Erdim
Yapi Kredi Bank


Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP
Back to top
Pinar
Guest
Posted: Tue Sep 20, 2005 8:51 am    Post subject: Re: SESTIMEOUT parameter Reply with quote
Neil,

Do you mean <Automatic Activation Limit> in APPC mode? If so it is zero.
thanks.

"Neil Pike" wrote:

Quote:
Pinar,

How many auto-activated LU6.2 sessions do you have?

We are using LU 6.2 sessions to access/run maniframe transactions. I
increased SESTIMEOUT registry parameter from 20 sec to 4 minute on HIS
server. So LU6.2 sessions will be kept open during 4 minute. Thus, HIS
server will try to use
existing sessions first. But after that change, number of sessions increased
on HIS server.
Why HIS server needs to open a new session evenif it has alreay free
one?What is the criterion of opening LU62 session?
What is the optimum value of SESTIMEOUT parameter? Is 4 minute right for us?
How can I determine correct value?

Thanks .
Pinar Erdim
Yapi Kredi Bank


Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP


Back to top
Neil Pike
Guest
Posted: Tue Sep 20, 2005 8:52 pm    Post subject: Re: SESTIMEOUT parameter Reply with quote
Set it to something. I have a funny feeling the sestimeout may only work if you
have some auto-activated sessions.

Quote:
Do you mean <Automatic Activation Limit> in APPC mode? If so it is zero.
thanks.

Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP
Back to top
Charles Ezzell (MSFT)
Guest
Posted: Wed Sep 21, 2005 4:51 pm    Post subject: Re: SESTIMEOUT parameter Reply with quote
Host Integration Server uses the SESTIMEOUT registry parameter to control
how long non-autostarted LU6.2 sessions are maintained (not UNBIND) after a
conversation ends. In this way, if another session is requested in this
time, the existing session is used without having to REBIND another one,
with a performance improvement (usually very small).

Setting the parameter to 0 (zero) the session will never be closed.

NOTE: It only applies to sessions that Host Integration Server is the
contention winner for.

There can be situations where the session will be closed in any case:
- If the APPC session ends abnormally, because the client issues a Cancel
request (CLOSE ERR message);
- A TP_ENDED hard, then we will likely UNBIND the session with an UNBIND
cleanup to make sure the condition is cleared.

HTH
Charles

"Neil Pike" <neilpike@compuserve.com> wrote in message
news:VA.0000631d.200a7763@compuserve.com...
Quote:
Set it to something. I have a funny feeling the sestimeout may only work
if you
have some auto-activated sessions.

Do you mean <Automatic Activation Limit> in APPC mode? If so it is zero.
thanks.

Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP

Back to top
Pinar
Guest
Posted: Thu Sep 29, 2005 4:51 pm    Post subject: RE: SESTIMEOUT parameter Reply with quote
Thanks for all replies.
Pinar

"Pinar" wrote:

Quote:
Hello,
We are using LU 6.2 sessions to access/run maniframe transactions. I
increased SESTIMEOUT registry parameter from 20 sec to 4 minute on HIS
server. So LU6.2 sessions will be kept open during 4 minute. Thus, HIS
server will try to use
existing sessions first. But after that change, number of sessions increased
on HIS server.
Why HIS server needs to open a new session evenif it has alreay free
one?What is the criterion of opening LU62 session?
What is the optimum value of SESTIMEOUT parameter? Is 4 minute right for us?
How can I determine correct value?

Thanks .
Pinar Erdim
Yapi Kredi Bank
Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Host Integration Server All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB