M204.2348: Difference between revisions
		
		
		
		Jump to navigation
		Jump to search
		
|  Automatically generated page update | 
| (No difference) | 
Latest revision as of 03:41, 14 March 2018
M204.2348 Subsystem record locking conflict
An attempt to enter a subsystem has tried to lock a set of records or a single record in a way that conflicts with another user's access. This message is issued when attempting to start or enter a service subsystem and the records cannot be locked. The locking conflict indicates that the service subsystem definition is being updated on the service node by another user.
Response: Wait a sufficient time for service node updates to complete, and retry.
Message attributes:
| RETCODEO=0 | Sets online return code | 
|---|---|
| RETCODEB=4 | Sets batch (single user) return code | 
| CLASS=E | Error class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter | 
| AUDITER | Writes the message with line type ER to the audit trail | 
| COUNT | Increments the error count (ERCNT) parameter |