Error 121 Logging

[anandpatwari31]

We face lot of problem in our MFG/Pro system due to Record Locking issue. We are thinking if can capture this message
"<file-name> in use by <user> on <tty>. Wait or press <STOP> to stop. (121)" in any output stream then it would be helpful to moniter the run time situation.
We are using openedge 10.1C .

Or it would be helpful if there is any logging of this error where we can come to know which user is locking whihc table during this time. We dont want to use VST as there has been serious impacts of this tables on system.

 

[TomBascom]

There is no general purpose filter that will capture record locking messages in the manner that you describe.

VSTs do not, by themselves, cause a serious impact.

Poor programming, especially with _Lock, can however have a very negative impact. The _lock table has no index and changes very rapidly. If -L is set to a large value and the system is busy with many locks it is quite possible for a query to consume a CPU and never complete. If you have several record lock conflicts being diagnosed in this way you will bring your system to its knees.

A better solution would be to use ProTop -- it is coded to avoid these issues. The "blocked sessions" screen will show you locking conflicts. You can also use PROMON, R&D, 1, 4, 2 ("Blocked Clients") to see what is going on more easily.