Currently the XREF output is extremely useful to determine index usage for queries and determine any potential full table scan.
An excellent addition to this would be if the output also include the lock status the query would use (NO-LOCK, EXCLUSIVE, SHARE-LOCK). This would provide information at compile time to check for default SHARE locks in the code that may have been overlooked. It would help prevent locking issues at development time.
I suggest that you add this as a new enhancement request in the Ideas forum so that other people can vote for it:
https://community.progress.com/businessusers/i/default.aspx
By the way, related to this issue, I have created an enhancement request for preventing SHARE-LOCKs:
https://community.progress.com/businessusers/i/openedge/possibility_to_prevent_share-locks.aspx
Also, in case you didn't know, there is a compile time parameter -NL (NO-LOCK) which makes record retrieval statements use NO-LOCK if the lock type is not explicitly given. That might be useful to prevent SHARE-LOCKs.