MSIR.1055 (caught) record locking conflict with user (unum) (uname) for file (file) record number (recnum): Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(Automatically generated page update) |
||
| Line 1: | Line 1: | ||
This informational message indicates that a record locking conflict has been handled by <var class="product">Model 204</var>. Depending on the setting of the [[RECLOCKO parameter]] these messages might be issued for caught or uncaught record locks. The default setting of RECLOCKO of X'03' means that when a site upgrades to <var class="product">Sirius Mods 8.1</var> or higher these messages might suddenly start appearing in the journal. If there are a large number of these, even of the "Caught" variety, it would suggest that it might be worth looking at the applications causing or encountering these messages, to reduce the frequency of record locking conflicts. | This informational message indicates that a record locking conflict has been handled by <var class="product">Model 204</var>. Depending on the setting of the [[RECLOCKO parameter]] these messages might be issued for caught or uncaught record locks. The default setting of RECLOCKO of X'03' means that when a site upgrades to <var class="product">Sirius Mods 8.1</var> or higher these messages might suddenly start appearing in the journal. If there are a large number of these, even of the "Caught" variety, it would suggest that it might be worth looking at the applications causing or encountering these messages, to reduce the frequency of record locking conflicts. | ||
[[Category:Sirius Mods | [[Category:Sirius Mods messages]] | ||
Revision as of 18:01, 19 April 2013
This informational message indicates that a record locking conflict has been handled by Model 204. Depending on the setting of the RECLOCKO parameter these messages might be issued for caught or uncaught record locks. The default setting of RECLOCKO of X'03' means that when a site upgrades to Sirius Mods 8.1 or higher these messages might suddenly start appearing in the journal. If there are a large number of these, even of the "Caught" variety, it would suggest that it might be worth looking at the applications causing or encountering these messages, to reduce the frequency of record locking conflicts.