MSIR.1055: Difference between revisions

From m204wiki
Jump to navigation Jump to search
No edit summary
m (misc formatting)
 
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.
This informational message indicates that a record locking conflict has been handled by Model&nbsp;204. Depending on the setting of the <var>[[RECLOCKO parameter|RECLOCKO]]</var> parameter, these messages might be issued for caught or uncaught record locks. </p>
 
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>
<b>Response:</b>
<b>Response:</b>
The X'03' default setting of <var>RECLOCKO</var> 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>
{{Template:MSIR.1055 footer}}
{{Template:MSIR.1055 footer}}

Latest revision as of 16:29, 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.

Response: 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.

Message attributes:

RETCODEO=0Sets online return code
RETCODEB=0Sets batch (single user) return code
CLASS=IInformation class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter
AUDITMSWrites the message with line type MS to the audit trail
NOCOUNTDoes not increment the error count (ERCNT) parameter

Back to list of messages