Re: Async comm not timing out

[Mark Lazarus <mlazarus@xxxxxxxx>]

Buck,

> I'm *not* using those columns on my READ to the async
>device.  Rather, I'm using columns 56-57: I/O error to trap the timeout.
>This way, I can check *STATUS and MAJMIN right in the mainline code
>rather than jump out to *PSSR.
>
>Now, recall that this code works perfectly to detect "normal" timeouts.
>It does not blow up or issue any "white messages" under any conditions.
>When the line fails, the timeout simply does not seem to occur.  
>It sits on the READ and control does not return to the RPG program at all.
>
>Have you seen this sort of thing before, and does using the *PSSR make
>a difference for you?

 The way I understand it, if the program is already in the *PSSR, then the
timeout can't be trapped by your READ w/ error indicator.

 -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
+---