QUICK on UNIX - Session Hang after Network Cutoff

[Deskin, Bob]

It would not help in terms of the link shutting down. What it would do
is allow each QUICK process that is cut off to shut itself down
gracefully. This would mean that you wouldn't have to hunt down leftover
processes. So it wouldn't help the user but it would help the
administrators.

Bob

-----Original Message-----
From: Robert Mills [mailto:robert.mills at pinnaclearvato.co.uk] 
Sent: January 31, 2008 10:14 am
To: Deskin, Bob; powerh-l at lists.sowder.com
Subject: RE: QUICK on UNIX - Session Hang after Network Cutoff

The setup we have here is that several users fire up enquiry screens
when that arrive in the morning and close them down when they go home.
The interval between enquiries ranges from a few seconds to 40+ minutes.
Investigation showed that the firewall the host sat behind would shut
the link if no data traffic was detected for 35 minutes.

Prior to the addition of the timed event within Reflection the user was
having to do something every 30 minutes (give or take a few) to get the
host to respond. This would reset the firewall activity counter.

Bob, How would setting the Terminal Time-out in QKGO helped here? Also,
what value would you have set it to?


regards,
 
Robert W.Mills
Business Systems Development Analyst
Group Information Systems & Technology
Pinnacle Arvato
DDI: +44 (0)20 8309 3604 


-----Original Message-----
From: Deskin, Bob [mailto:Bob.Deskin at Cognos.COM] 
Sent: 31 January 2008 14:11
To: Robert Mills; Abd Ghani Abdullah; powerh-l at lists.sowder.com
Subject: RE: QUICK on UNIX - Session Hang after Network Cutoff

You could also set the Terminal Time-Out in QKGO.
 
Bob


________________________________

	From: powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com
[mailto:powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com] On
Behalf Of Robert Mills
	Sent: January 31, 2008 5:10 am
	To: Abd Ghani Abdullah; powerh-l at lists.sowder.com
	Subject: RE: QUICK on UNIX - Session Hang after Network Cutoff
	
	
	Hi Ghani,
	 
	This sounds like the problem that we had last year. We fixed it
by setting up an event within Reflection that emulated the pressing of a
'null action' function key (in our case it was F12) if the user had not
done anything within the previous 30 minutes.
	 
	 
	regards,
	 
	Robert W.Mills
	Business Systems Development Analyst
	Group Information Systems & Technology
	Pinnacle Arvato
	DDI: +44 (0)20 8309 3604 

	 

________________________________

	From:
powerh-l-bounces+robert.mills=pinnaclearvato.co.uk at lists.sowder.com
[mailto:powerh-l-bounces+robert.mills=pinnaclearvato.co.uk at lists.sowder
 
     This message may contain privileged and/or confidential information.  If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so.  Thank you.