M204.1216
M204.1216 Record locking conflict
A SOUL request or an attempt to enter a subsystem has tried to lock a set of records or a single record in a way which conflicts with another user's access. This message may be followed by message M204.1076, Do you really want to try again?.
Response: If you think that the other user is sure to give up the access to the records you want, you can answer Y and another attempt will be made. You can wait before answering to give the other user more time to finish working
with the records.
However, by answering YY, you may create a deadlock with another user, where you cannot continue without access to records the other user holds and the other user cannot continue without access to records you hold. When
this happens, Model 204 repeats this message and the prompt to retry. You should consider answering N to let the other user continue.
If you choose not to retry the enqueue or if you are not given a chance to retry, wait until you think the records have become available and retry the entire request or command. Consider revising the application to include an On Record Locking Conflict unit which will be invoked in the event of a record locking conflict. Refer to On units for more information on On units.
System manager response: If this message occurs often, some Model 204 applications probably are poorly written and hold enqueues on record sets even when it is wrong to do so (during user screen interaction, for example). Review programming for record enqueueing in Managing record locking, or contact Technical Support.
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 |