Greg,

I still need more details. What are you writing to, disk file, msg file,
terminal, socket, etc. All but sockets and msg files require PM for
no-wait I/O. If you're writing to a disk file and you're not priv, then
when the fwrite returns, it's written, not necessarily flushed to disk
though. If msg file, if the file is full the fwrite will wait until
there is more space. With msg files, you can open no-wait, call fcontrol
to set a timeout, call fwrite, then call iowait. Iowait will then return
with success or timeout. This is just a sample, explain what you want to
write to.

John Zoltak
North American Mfg Co

> -----Original Message-----
> From: Stigers, Greg ~ AND [SMTP:[log in to unmask]]
> Sent: Wednesday, April 15, 1998 3:43 PM
> To:   [log in to unmask]
> Subject:      Re: [HP3000-L] The time has come
>
> I have received some responses, all of them explaining timed reads.
> Sorry for any confusion; not only was I not clear, I apparently
> conveyed
> the opposite of what I wanted to say. Maybe I should look to turn that
> into a job skill...
>
> I think that I have timed reads working. I need to validate that what
> the app tried to write 'got written' within a timeout, or failed
> within
> that timeout, if that is possible.
>
        <snip>