Phil is correct in thread 006857, in that using the lock cookie is not guaranteed to identify the client.
Some of the proposals in that thread for what to use as a lock cookie would make it very easy for any client to unlock a record for which they do not own the lock (e.g. if you used the record number as the cookie then it is trivial to unlock a record, likewise if you used an incremental number).
However, if you are using the Random class to generate the cookie, then you are going to get a random number somewhere between 9223372036854775807 and -9223372036854775808. It is no longer a trivial matter to determine a potential cookie for a lock you don't own (unless you use a constant seed for your random number).
So for all intents and purposes, if the same cookie is used in two subsequent calls, then you might want to assume that the same client is calling both methods. There is no guarantee that the same client is calling both methods, but it is a reasonable assumption.
If you want to guarantee that the client who locks the record is the only client who can then modify it or unlock it, then you will need to ignore the cookie as an identification mechanism, and look at an RMI Connection Factory or a Sockets based solution.
(Short answer: you might want to go with the assumption, and make a comment in your design decisions document about why you did not go for a more complex solution ).
There are at many different assignments being worked on by different candidates. Some are so similar that it is difficult to work out what the differences are. And some are very obviously different. See the SCJD FAQ for more information about variants of assignments.
The "Fly By Night Services" assignment had a "readme.txt" file. The newer assignments have (I think) a "versions" file and a "choices" file which between them have much the same information. (The readme.txt file also described the file layout, but the new assignments tell you how you must layout your files, so this does not apply to you).
Bottom line: follow your instructions, not anyone else's. So don't bother trying to create a "readme.txt" file if your instructions don't require it.