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
m (minor formatting) |
(Automatically generated page update) |
||
| Line 3: | Line 3: | ||
The X'03' default setting of <var>RECLOCKO</var> 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 might be worth examining the applications causing or encountering these messages, and making changes to reduce the frequency of record locking conflicts. | The X'03' default setting of <var>RECLOCKO</var> 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 might be worth examining the applications causing or encountering these messages, and making changes to reduce the frequency of record locking conflicts. | ||
[[Category:MSIR.1000 - MSIR.1199]] | [[Category:MSIR.1000 - MSIR.1199]] | ||
Latest revision as of 23:40, 3 March 2017
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 X'03' default setting of RECLOCKO 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 might be worth examining the applications causing or encountering these messages, and making changes to reduce the frequency of record locking conflicts.