Title: | DECnet-VAX Conference |
Notice: | The WORLD's Leader in Networking |
Moderator: | BULEAN::BENOIT |
Created: | Sun Feb 02 1986 |
Last Modified: | Sun Jun 01 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 5887 |
Total number of notes: | 24029 |
Hi, a customer of mine try to use a timeout in a $QIOW read operation in a "transparent" task-to-task program . IO$M_TIMED function modifier doen't seem to work in this context... Any ideas ? Philippe, TSC Evry.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
5871.1 | not supported | RMULAC.DVO.DEC.COM::S_WATTUM | Scott Wattum - FTAM/VT/OSAK Engineering | Thu Feb 13 1997 16:59 | 7 |
you cannot do timed reads to netdriver. your only option is to set up your own timer, and then have an ast routine do what is necessary (such as cancel i/o on the channel, or disconnect); or don't use QIOW. --Scott | |||||
5871.2 | ASTs | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Fri Feb 14 1997 09:24 | 15 |
The $qio[w] modifiers are highly device-specific -- do *not* assume that any particular modifier works on any particular device. And beware -- the bit underneath a modifier such as IO$M_TIMED might do something *quite* unexpected when used on j-random device driver. (Even the main operation codes are somewhat device-specific...) Teach the customer about ASTs -- they'll probably never go back to using time-outs. If the customer *needs* a timeout, use the asynchronous version of the call with an IOSB, a $setimr, and the $cancel call. (I'd tend to avoid this construct, as it tends to be infested with timing-related problems if not coded carefully and correctly.) |