M204.1701: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
 
m (add <var>'s)
 
Line 1: Line 1:
{{Template:M204.1701 skeleton}}
{{Template:M204.1701 skeleton}}
<P>Model 204 has detected a uniqueness conflict while processing a REDEFINE FIELD command, Z command, or the index update portion of a FILELOAD command. Processing continues so that all conflicts that exist may be reported.
<P>
In the case of REDEFINE, the REDEFINE operation is undone. In the case of the Z and FILELOAD commands, the file is marked physically inconsistent. </P>
Model 204 has detected a uniqueness conflict while processing a <var>REDEFINE FIELD</var> command, <var>UNIQUE</var> command, or the index update portion of a <var>FILELOAD</var> command. Processing continues so that all conflicts that exist may be reported.
<p><b>Response:</b> Take steps to resolve uniqueness conflicts, either by altering input data where appropriate, or by deleting duplicate records or fields. Then reissue the command. </p>
In the case of <var>REDEFINE</var>, the <var>REDEFINE</var> operation is undone. In the case of the <var>Z</var> and <var>FILELOAD</var> commands, the file is marked physically inconsistent. </P>
<p>
<b>Response:</b> Take steps to resolve uniqueness conflicts, either by altering input data where appropriate, or by deleting duplicate records or fields. Then reissue the command.  
</p>
{{Template:M204.1701 footer}}
{{Template:M204.1701 footer}}
<!-- skeleton as it was in pdf/NON-UNIQUE VALUE value FOUND FOR FIELD fieldname IN RECORD NUMBER recno; CONFLICTS WITH RECORD NUMBER recno /-->
<!-- skeleton as it was in pdf/NON-UNIQUE VALUE value FOUND FOR FIELD fieldname IN RECORD NUMBER recno; CONFLICTS WITH RECORD NUMBER recno /-->

Latest revision as of 18:47, 9 March 2018

M204.1701  Non-unique value token found for field token2 in record number token3; conflicts with record number token4

Model 204 has detected a uniqueness conflict while processing a REDEFINE FIELD command, UNIQUE command, or the index update portion of a FILELOAD command. Processing continues so that all conflicts that exist may be reported. In the case of REDEFINE, the REDEFINE operation is undone. In the case of the Z and FILELOAD commands, the file is marked physically inconsistent.

Response: Take steps to resolve uniqueness conflicts, either by altering input data where appropriate, or by deleting duplicate records or fields. Then reissue the command.

Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets 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

Back to list of messages