You're lucky. I encountered this problem when I enhanced Webshare to
support BFS files. Here an
an extract of the REXX exec that reads (and now also closes) a BFS file:
'CALLPIPE HFS' fn '| *:'
/* HFS seems to leave files open. So: close the OE Luw */
/* call apiload 'VMREXOVM' ==> not required */
parse value 1 2 with function_code Bufflen Buff
address OPENVM 'BPX1VM5 function_code bufflen buff',
'return_value return_code reason_code'
Note that I avoid the overhead of calling APILOAD by using numbers and
base function names instead of the more userfriendly stuff one would find
in the manuals.
Kris,
IBM Belgium, VM customer support
> Thanks to Miguel's note, I figured out what the message means. However,
> I'm still struggling to deal with the problem. Perhaps someone else
> has run into this type of problem???
> I have a web server on VM that is creating the file in BFS. (It is
doing
> a OPENVM PUTBFS to get the file into the file system.) The CGI
continues
> on its way and finishes with no problem. However, it looks like the
file
> is never "closed". To anything else, including another web server, the
> file is "busy". So, if one of the others tries to modify the file, it
cannot.
> If this were a straight forward CMS app, I'd do a
> FINIS to make sure the file was closed. However, I don't work with OE
> very much and have no idea if there is a way to do this in BFS.
> Any ideas/suggestions?
> Martha
