Kris Buelens wrote :-
> You could use Q FILEPOOL CONFLICT to see wait conditions
> SFS guarantees read integrity, that is, if someone has a file in read,
SFS keeps that image
> of the file until the last reader closes it (this image is kept in
shadow tables).
> And -just tested- you can ind
You could use Q FILEPOOL CONFLICT to see wait conditions
SFS guarantees read integrity, that is, if someone has a file in read, SFS
keeps that image of the file until the last reader closes it (this image is
kept in shadow tables). And -just tested- you can indeed ERASE the file
while someone has
Sorry for the long preamble but I need to explain what I see happening :_
I inherited an application that was not very well designed or written but
is too complex an critical to make wholesale changes. The way it works is
that :-
1) Server A loads a cumulative log into an SFS (file control
