This worked. Could there be another directive that allows a program that's open for input to ignore the lock anyways? Seems to us that even if it is open for I-o in one program, the program open for input only should not have been affected - with out needing to use the "ignore lock" phrase.
↧