Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!mit-eddie!genrad!decvax!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: disk xqp code example -- request
Message-ID: <870718162147.06h@CitHex.Caltech.Edu>
Date: Sat, 18-Jul-87 19:21:51 EDT
Article-I.D.: CitHex.870718162147.06h
Posted: Sat Jul 18 19:21:51 1987
Date-Received: Sun, 19-Jul-87 22:42:41 EDT
References: <2550@husc6.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 14


 > I would like to write some data to disk without the overhead of RMS.   I've
 > tried  to  use IO$WRITEVBLK as described in the I/O manual, but despite the
 > $QIOW returning success, I find that no data has made it.   I  $CREATE  the
 > file  with  RMS,  save  the  FID for the subsequent I/O calls, etc.  I also
 > extend the file before I access it.  The extend works fine.

Sounds like you're making the mistake (common for neophytes) of assuming  that
the value returned by SYS$QIOW tells you whether the I/O request did anything.
The status returned by SYS$QIOW tells  you  whether  the  request  was  QUEUED
successfully  (that's  what  QIO stands for:  Queue I/O request).  To find out
whether the I/O request succeeded, you need to look at the value  returned  in
IOSB,  and I suspect that if you do so, the reason for the failure will become
obvious to you.