From m204wiki
Revision as of 22:21, 15 March 2018 by JAL (talk | contribs) (add link)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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.

Message attributes:

RETCODEO=24Sets online return code
RETCODEB=24Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITERWrites the message with line type ER to the audit trail
COUNTIncrements the error count (ERCNT) parameter
SAVESaves the message in the VIEW ERRORS table

Back to list of messages