|
|
|
In the multi-threaded FPUTFGET operational model on Unix systems, a call to release a record lock could release a lock held by another thread when recursive lock support was enabled. This could cause data to become inconsistent, leading to error 158 or 160. In another situation, faulty unique file ID generation could cause data consistency errors. The logic has been corrected to handle these situations.
