<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
Hi Ghani:<BR>
<BR>
<BR>
Did you try Adrian's suggest?<BR>
i.e. <FONT face=Arial>You could try trapping hang ups and terminates.</FONT> <BR>
<FONT face=sans-serif size=2>For interactive users executing Quick, add this to one </FONT><BR>
<FONT face=sans-serif size=2> of the early lines of their profiles (or the system profile)</FONT> <BR><FONT face=sans-serif size=2> trap "exit 0" HUP TERM</FONT><BR>
<FONT face=Arial> </FONT><BR>
<FONT face=Arial> I am not sure whether the trap will be in scope as </FONT><BR>
<FONT face=Arial> QUICK might be do its own trap setting. It might be worth a try.</FONT><BR>
<BR>
Has the data communcation hardware changed recently?<BR> <BR> Some hardware settings cause the communication devices <BR> to disconnect when certain control characters are received.<BR> <BR> I believe control-B for example is often associated with data <BR>
terminal ready (DTR) .<BR> <BR> The control characters are almost always setup for various <BR>
functions in the QKGO. In-field editing, etc. For example, <BR>
control-B is usually DATA RECALL.<BR> <BR> Bad floresent light ballasts can emit spurious signals <BR> onto communciation lines. So can other devices. <BR> Every so often you might get a disconnect signal.<BR>
<BR>
If XON/XOFF is enabled a spurious XOFF could cause<BR>
the session to wait.<BR>
<BR> Keep you communication lines well shielded if possible.<BR> <BR> I have heard of some people getting success by grounding pin 20<BR> on an RSR 232 connector. To me, this is extreme! <BR> <BR>
I would talk to my hardware people and make sure there are no<BR> control characters that can cause a disconnect.<BR> <BR><BR> Regards,<BR> Peter <BR><BR><BR>
<BLOCKQUOTE><BR><BR><BR><BR> </BLOCKQUOTE><br /><hr /> <a href='' target='_new'></a></body>
</html>