RE: Weird V5R1 actions with IFS files

You create a file, then close it, then open in... in a lot of OSes a 0 byte
file doesn't really exist until something is written to it.  It has to
contain SOMETHING to actually be written.  Instead of Creating, closing,
opening, writing, closing, why not just try Creating, writing, closing and
see if that works.

Regards,

Jim Langston

-----Original Message-----
From: Mike Silvers [mailto:msilvers@hbs-inc.com]

Hi all.

I am using the IFS file api's open, close, and write to create a file, close
it, open it, write to it, and close it again.  I follow along in debug.
There is a file descriptor when the file is opened and when it is closed the
return integer is 0 (the correct value).  When I look at the IFS, the file
does not exist.  I searched the entire IFS...no luck.  The file simply does
not exist.  When I am looking for the file, I use a QSECOFR profile, so
permissions are not an issue.  It is really weird.  Anyone else have any
experiences with this?  Anyone have any ideas?

Mike