So I have a resource manager that implements io-open, io-close, and io-stat.  To my understanding (based on qnx's 
website) the stat() function is implemented as a single combined message that causes an open, stat, close (prehaps with 
some ocb locking in there) message to be fed to my ResMgr's io handler functions.

Looking at the example of readblock I noticed that by returning an error from the lseek() handler, would cause the io-
read handler to not be called at all, so my assumption is that this is similar for stat, however I wanted to know if my 
assumption is true.

In my case there are times where I can and will respond to the io-open with a failure, however it seems that my io-stat 
function is still being called, even though it would seem that it shouldn't be.   Is there some special way I need to 
deal with this combined message in my io-open or io-stat routines?

Btw: in the case of an open failure condition i am NOT calling iofunc_open_default(), I am simply returning an errno 
value other than EOK.

Any advice with this issue would be greatly appreciated.

Thanks,

Josh