M204.1934: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
 
No edit summary
 
Line 1: Line 1:
{{Template:M204.1934 skeleton}}
{{Template:M204.1934 skeleton}}
<P>
<P>
An attempt is being made to turn off [[Transaction backout|transaction backout]] with the RESET command for a file that has some field-level constraints defined. For example, the file might contain at least one field with the UNIQUE or AT-MOST-ONE attribute. </p>
An attempt is being made to turn off [[Transaction back out|transaction backout]] with the <var>[[RESET command|RESET]]</var> command for a file that has some [[Field_design#Field_and_content_constraints|field-level constraints]] defined. For example, the file might contain at least one field with the UNIQUE or AT-MOST-ONE attribute. </p>
<p>
<p>
Field-level constraints cannot be fully enforced in non-TBO files. Model&nbsp;204 will issue the following prompt, and it will discontinue RESET processing or proceed according to the response received: </P>
Field-level constraints cannot be fully enforced in non-TBO files. Model&nbsp;204 will issue the following prompt, and it will discontinue RESET processing or proceed according to the response received: </P>

Latest revision as of 22:58, 15 March 2018

M204.1934  File fileName has field-level constraints defined moreInfo

An attempt is being made to turn off transaction backout with the RESET command for a file that has some field-level constraints defined. For example, the file might contain at least one field with the UNIQUE or AT-MOST-ONE attribute.

Field-level constraints cannot be fully enforced in non-TBO files. Model 204 will issue the following prompt, and it will discontinue RESET processing or proceed according to the response received:

DO YOU REALLY WANT TO TURN OFF TRANSACTION BACKOUT?

File manager response: The consequence of turning off TBO for files with field-level constraints defined is that records that violate those constraints can be stored in Table B (though they will be left logically deleted). If this is an acceptable situation and it is necessary to disable transaction backout, respond Y to the prompt. If this is an unacceptable situation, respond N.

Message attributes:

RETCODEO=0Sets online return code
RETCODEB=0Sets batch (single user) return code
CLASS=IInformation class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter
AUDITMSWrites the message with line type MS to the audit trail
NOCOUNTDoes not increment the error count (ERCNT) parameter

Back to list of messages