Locking message 2624 does not report accurate data for all users when record is released

Locking message 2624 does not report accurate data for all users when record is released.
Native locking message 2624 does not report the real user in case of queuing.
Does the message 2624 update automatically? 

Example:
- 3 users: User1, User2, User3 are connected to sports2000 db
- in this order they run following code:

FIND FIRST customer EXCLUSIVE-LOCK .
MESSAGE USERID("dictdb") "keeps a lock on first customer record" VIEW-AS ALERT-BOX INFO BUTTONS OK.

- User2 and User3 both get message 2624 saying the customer record is locked by User1
- User1 releases the record and User2 is updated (2624 disappears), however User3 still see the 2624 message that User1 is locking the record

This is expected behavior. There is no automatic refresh of 2624 message. This message reflects the state of the record in the time when the lock was requested.

Updating of 2624 message can be achieved by using Lock Wait Timeout (-lkwtmo) startup parameter at the beginning of the session, set it to for example 5 seconds and then ON STOP rerun the code as follows:

DO ON STOP UNDO, RETRY:

   FIND FIRST customer EXCLUSIVE-LOCK .
   MESSAGE USERID("dictdb") "keeps a lock on first customer record" 
                                          VIEW-AS ALERT- BOX INFO BUTTONS OK.

End.

In above scenario 2624 message is updated every 5 seconds with accurate data who is locking the record.

References to Other Documentation:

 What is the -lkwtmo parameter used for?