Are you setting the copy serialization to static/shared static/dynamic/
or shared dynamic? I would think that shared dynamic would allow TSM to
grab the file if nothing is being written to it, then release back when
done. Unless there's an APAR on not releasing the file handle, I don't
see why it wouldn't let go after it backs it up.

MO

On Tuesday, June 5, 2001, at 12:54 PM, Brecton Whitten wrote:

*SMer's,

  In searching the postings, I did not see a solution
concerning the question I currently have. Does
anyone out there backup Btrieve databases without
stopping them first? I am somewhat familiar with OFM
from St. Bernard as we use it on other clients. The problem
we are having seems to be that TSM gets exclusive control
of Btrieve files and does not release it.

  Our environment is TSM server/client 4.1.2 , Netware 4.11,
and Btrieve 6.15. I have been told that stopping Btrieve on a
nightly basis to do a backup is not an option for this client.

 If anyone has slain this dragon before, I would appreciate
your input.

                                                             Brec
Whitten

bwhitten AT uabmc DOT edu