QUICK on UNIX - Network Cutoff

[Peter Bateman]

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20080204/9c76bad8/attachment.htm