Re: Zero IOSB status

From: Hein (hein.nomail_at_hp.nomail.com)
Date: 03/31/05


Date: Thu, 31 Mar 2005 13:13:23 GMT


"Ron Atkinson" <oj_287@yahoo.co.uk> wrote in message
news:1112267525.611587.217520@f14g2000cwb.googlegroups.com...
> When performing a QIO READVBLK + IO$M_LOCKBUF on an IP listening
> socket, the QIO status is OK but the read IOSB status is returning the
> value 0 instead of 1.

The QIO status OK shows that the QIO has succesfully started and that you
can expect an AST (if you requested one) and a valid IOSB when the operation
is done.

The 0 in the IOSB says the IO is not done. Hang around some more (debugger!)
and it will change\
Did yo mean to issue QIO or did you perhaps need QIOW?
Check out SYS$SYNCH?

>> What am I doing wrong ?

you are not waiting when you should, or ask the system (QIOW) to do the wait
for you?

Hein.



Relevant Pages

  • Re: Zero IOSB status
    ... where the QIO EFN was being set *before* the IOSB ... P.s. the common IO completion routines ...
    (comp.os.vms)
  • Re: Zero IOSB status
    ... > Ron Atkinson wrote: ... >> socket, the QIO status is OK but the read IOSB status is returning the ...
    (comp.os.vms)
  • Re: Zero IOSB status
    ... > socket, the QIO status is OK but the read IOSB status is returning the ... > When I step through this bit of code using the pascal debugger it ...
    (comp.os.vms)
  • Re: Zero IOSB status
    ... > The QIO status OK shows that the QIO has succesfully started and that you ... > can expect an AST and a valid IOSB when the operation ... Hoi Hein, ... before the event flag is posted. ...
    (comp.os.vms)
  • Re: Problem with UCX QIOW IO$_SETMODE
    ... The trick is that, with the QIO interface, you must not specify all ... parameter p5 which is used to set socket options. ... A-1010 Vienna / AUSTRIA ...
    (comp.os.vms)