MSIR.1056 (type) (strength) lock was obtained by user (usernum) at (time): Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (add comma) |
||
| Line 1: | Line 1: | ||
This message provides information about a record locking conflict to supplement information about the conflict that is provided by message [[MSIR.1055 (caught) record locking conflict with user (unum) (uname) for file (file) record number (recnum)|MSIR.1055]]. | This message provides information about a record locking conflict to supplement information about the conflict that is provided by message [[MSIR.1055 (caught) record locking conflict with user (unum) (uname) for file (file) record number (recnum)|MSIR.1055]]. | ||
This message was originally issued to provide more details on untrapped record locking conflicts when the <var>[[RECLOCKO parameter|RECLOCKO]]</var> parameter X'04' bit was set. As of <var class="product">Model 204</var> 7.5 that bit setting is obsolete and this message will appear if the X'01' or X'02' bit is set. | This message was originally issued to provide more details on untrapped record locking conflicts when the <var>[[RECLOCKO parameter|RECLOCKO]]</var> parameter X'04' bit was set. As of <var class="product">Model 204</var> 7.5, that bit setting is obsolete, and this message will appear if the X'01' or X'02' bit is set. | ||
[[Category:MSIR.1000 - MSIR.1199]] | [[Category:MSIR.1000 - MSIR.1199]] | ||
Latest revision as of 16:17, 16 April 2018
This message provides information about a record locking conflict to supplement information about the conflict that is provided by message MSIR.1055.
This message was originally issued to provide more details on untrapped record locking conflicts when the RECLOCKO parameter X'04' bit was set. As of Model 204 7.5, that bit setting is obsolete, and this message will appear if the X'01' or X'02' bit is set.