[Info-vax] Timeout in a write using QUIW.

Jan-Erik Söderholm jan-erik.soderholm at telia.com
Thu Jun 22 02:54:15 EDT 2023


Den 2023-06-22 kl. 00:19, skrev Stephen Hoffman:
> On 2023-06-21 21:39:19 +0000, Jan-Erik Sderholm said:
>>
>> My thought was to just queue the I/O, wait a sec or two using $WAIT and 
>> then check the IOSB. If not completed OK, CANCEL and return an error to 
>> the application...
>>
>> We'll see. Hopefully we can convince them to install wired connections 
>> instead of using Wifi...
> 
> Yeah. I tried that in the 1980s. Learned that ASTs and threads and 
> completion routines avoided a whole lot of the mess that the inevitable 
> errors within sync I/O and networking involves. You're headed for some 
> races here, too.
> 
> 

Yes, there are some "unknowns" in this. :-)
Equipment gets restarted or powered off. Network is "flaky".

Most of the reconnect issues are handled by the telnet driver
by creating TNA devices that are used for the communication.

The connections are reconnected after a equipment restart or
network autage automatically with no application involvment.

And the programming is easier by just pretending that all network
equipment are "terminals" having a TNA device.

Thanks for your input!

Jan-Erik.



More information about the Info-vax mailing list