MSIR.0437 Value of (string) for field (field) maps to SIRFIELD exception value or different format pair: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
(Automatically generated page update)
Line 10: Line 10:
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 <var class="book">[http://m204wiki.rocketsoftware.com/images/4/4b/SirfieldNew.pdf Sir2000 Field Migration Facility Reference Manual]</var>. If this still presents a problem for you, please call [[Contacting Rocket Software Technical Support|Technical Support]].  
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 <var class="book">[http://m204wiki.rocketsoftware.com/images/4/4b/SirfieldNew.pdf Sir2000 Field Migration Facility Reference Manual]</var>. If this still presents a problem for you, please call [[Contacting Rocket Software Technical Support|Technical Support]].  


{{Template:MSIR.0437 footer}}
[[Category:Sirius Mods messages]] [[Category:MSIR.0400 - MSIR.0599]]
[[Category:Sirius Mods messages]] [[Category:MSIR.0400 - MSIR.0599]]

Revision as of 19:20, 11 July 2016

This message indicates that an LAI statement was issued in a FLOD program, and the unloaded file contained value string for loading into field field which matched a primary, alternate, or ERROR format. The load did not succeed, because 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.


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