× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Async comm not timing out
  • From: Mark Lazarus <mlazarus@xxxxxxxx>
  • Date: Tue, 23 Dec 1997 22:39:27

Buck,

>This week's question is for the communications programmers.
>I have an async program that does an invite, then a read.
>The WAITRCD is set to 15 seconds, and works most of the 
>time.  The situation where it doesn't work is when I 
>have lots of parity errors on the line.  What happens is...
>nothing.  The line, controller and device all show ACTIVE
>but the READ doesn't time out.  If I cancel the job, the
>controller and device go to FAILED.  If I vary the line, 
>ect. off and on and re-start the job, everything works fine 
>until the parity errors pile up again.

 I'm going to guess at what is happening here.  You have a *PSSR routine to
do processing for the timeout condition.  When getting those line errors,
the program goes into the *PSSR.  What is probably going on is that the
timeout occurs during error processing, creating an error upon error
condition.  

 I think the solution is to explicitly test for those error conditions in
your subroutine.  Maybe you should post the pgm code?
 
 -mark

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.