FYI, in the Release notes for 10.2.2, there are these two corrections
related to "locking":
8776 Due to the fix for Issue 7691, locks may have been left on a
dynamic file if the client timeout occurred while the program
on the server was updating a dynamic file. This problem has
been fixed.
9187 When logging of a UniVerse telnet session, using either
the QUIT or OFF commands, an application error similar to
the following example occurred:
Source : IBM UniVerse
Category: None
Event ID: 1004
Description: UniVerse error: Wait for server threads
failed.
Win32 error: 6. The handle is invalid..
This problem has been fixed.
Note: This issue could also result in user login information
being incorrectly maintained and displayed through the
uvlictool and the LISTU command after the user logged
off. In certain situations, a lock associated with the
user might also be left behind.
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
