M204.2123 Value specified violates binary data type validation in record token, field ignored: token2 = token3
An attempt was made to store invalid data into a BINARY field in a Numeric Validation file. For SOUL or Host Language Interface, the request is canceled following the above message; the transaction is backed out, as TBO is a Numeric Validation requirement. For Fastload (FLOD or FILELOAD), the above message is issued without cancellation, the field is dropped and the file is marked "logically inconsistent."
Response: For SOUL or Host Language Interface, correct the input data to be a valid BINARY number, and resubmit the transaction.
For Fastload (FLOD or FILELOAD), make note of all Numeric Validation violations for the run, and construct one or more updates to the file that supply the correct BINARY data values. The File Manager (see below) must RESET the FISTAT parameter to X'00' prior to running the correctional updates. If the Fastload was written such that decisions were made based on an anticipated BINARY field update, the entire Fastload should be re-run after correcting the invalid BINARY field input — this type of error situation is the reason behind the "logically inconsistent" warning.
File manager response: For SOUL or Host Language Interface, no response is necessary.
For Fastload (FLOD or FILELOAD), reset the FISTAT parameter to X'00' once the user is ready to submit correct BINARY data input. FISTAT has been set to X'40' as a reminder that the current state of the file may be "logically inconsistent," depending on how the Fastload was written.
|RETCODEO=0||Sets online return code|
|RETCODEB=4||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|
|CANCEL||Cancels the user's request|
|COUNT||Increments the error count (ERCNT) parameter|