MSIR.1055: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Template:MSIR.1055 skeleton}} | {{Template:MSIR.1055 skeleton}} | ||
<p> | <p> | ||
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. | |||
</p> | </p> | ||
<p> | <p> | ||
Revision as of 14:42, 14 May 2018
MSIR.1055 token0 record locking conflict with user token2 (token3) for file token4, record number token5
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.
Response:
Message attributes:
| RETCODEO=0 | Sets online return code |
|---|---|
| RETCODEB=0 | Sets batch (single user) return code |
| CLASS=I | Information class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter |
| AUDITMS | Writes the message with line type MS to the audit trail |
| NOCOUNT | Does not increment the error count (ERCNT) parameter |