M204.2120 AT-MOST-ONE violation during Store Record in a non-TBO file
An AT-MOST-ONE Field-Level Constraint violation during a Store Record or IFSTORE has occurred, and Transaction back out (TBO) was previously disabled for the file. Preceded by message M204.2119.
When TBO is disabled and an AT-MOST-ONE violation occurs as part of a Store Record, the record being stored remains in Table B, and indexing for any fields already processed/stored remains in Tables C and D. The record is logically deleted. Regardless of whether or not an On Field Constraint Conflict unit exists for the request, the request is canceled accompanied by a hard restart. The file is left in a physically inconsistent state.
Response: This type of integrity violation in a non-TBO file cannot be remedied by the On Field Constraint Conflict unit, as On FCC never gets invoked. It is therefore inadvisable to update fields with Field-Level Constraints while the file is TBO-disabled. Contact your File Manager.
File manager response: The file must be reorganized.
|RETCODEO=24||Sets online return code|
|RETCODEB=24||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|
|SAVE||Saves the message in the VIEW ERRORS table|