MSIR.0416 Date maps to exception value or different format pair in (file) record (rec) (value) = (field)
This message indicates that an update to record number rec in file file for field field was attempted, and that the value being stored matched a format and cannot be stored in the record. The reason it cannot be stored is that field is related to another field, field2, and there is a conflict among the exception values, primary, alternate, and/or error formats specified on a SIRFIELD RELATE command naming the two fields.
value, when converted to a format for field2, results in value2:
- If value2 is an exception value for field2, the update is not allowed (because, since value matched a format, it is not also an exception value).
- Otherwise, it is a conflict with formats. Value2 matches an earlier format for field2 than the format which matched value.
This is a very rare error message; if you receive it you should review your use of a valid date as an exception value, and your use of the ALTERNATES and ERROR clauses, as discussed in the Sir2000 Field Migration Facility Reference Manual. If this still presents a problem for you, please call Technical Support.
The update attempt was from User Language or IFAM. If the attempted update is from the FILE RECORDS UNDER statement or from the IFFILE function, rec will be -1, and, for FILE RECORDS UNDER, M204.1096 THERE WERE NO UPDATES FOR BACKOUT TO PROCESS is also issued.
The update is rejected and the request is cancelled (for an IFAM request, a user restart is performed).
Message attributes:
| 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 |
| COUNT | Increments the error count (ERCNT) parameter |