M204.2117: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (add link)
m (remove 0 from token0)
Line 2: Line 2:


<P>
<P>
This error message is issued when a <var class="term">token0</var> field attribute definition is attempted on any file with [[Transaction back out]] (TBO) disabled. TBO must be active to <var>DEFINE</var> or <var>REDEFINE</var> a field as <var class="term">token0</var>. While TBO may be disabled (with warnings) once a Field-Level Constraint has been defined, it is highly recommended that this practice be avoided to protect the data integrity of the file. </P>
This error message is issued when a <var class="term">token0</var> field attribute definition is attempted on any file with [[Transaction back out]] (TBO) disabled. TBO must be active to <var>DEFINE</var> or <var>REDEFINE</var> a field as <var class="term">token</var>. While TBO may be disabled (with warnings) once a Field-Level Constraint has been defined, it is highly recommended that this practice be avoided to protect the data integrity of the file. </P>
<p>
<p>
<b>File manager response:</b> Activate TBO by reseting <var>FRCVOPT</var> to X'00', and proceed with the <var>DEFINE</var>/<var>REDEFINE</var> of the field to <var class="term">token0</var>.  
<b>File manager response:</b> Activate TBO by reseting <var>FRCVOPT</var> to X'00', and proceed with the <var>DEFINE</var>/<var>REDEFINE</var> of the field to <var class="term">token</var>.  
</p>
</p>
{{Template:M204.2117 footer}}
{{Template:M204.2117 footer}}
<!-- skeleton as it was in pdf/AT-MOST-ONE FIELDS CANNOT BE DEFINED IN A NON-TBO FILE /-->
<!-- skeleton as it was in pdf/AT-MOST-ONE FIELDS CANNOT BE DEFINED IN A NON-TBO FILE /-->

Revision as of 21:30, 26 March 2018

M204.2117  token fields cannot be defined in a non-TBO file

This error message is issued when a token0 field attribute definition is attempted on any file with Transaction back out (TBO) disabled. TBO must be active to DEFINE or REDEFINE a field as token. While TBO may be disabled (with warnings) once a Field-Level Constraint has been defined, it is highly recommended that this practice be avoided to protect the data integrity of the file.

File manager response: Activate TBO by reseting FRCVOPT to X'00', and proceed with the DEFINE/REDEFINE of the field to token.

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