MSIR.0437 Value of (string) for field (field) maps to SIRFIELD exception value or different format pair: Difference between revisions
(Automatically generated page update) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
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. | 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'': | |||
<ul> <li>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). <li>Otherwise, it is a conflict with formats. ''value2'' matches an earlier format for ''field2'' than the format which matched ''''value''''.</ul> | <ul> | ||
<li>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). | |||
<li>Otherwise, it is a conflict with formats. ''value2'' matches an earlier format for ''field2'' than the format which matched '''''value'''''. | |||
</ul> | |||
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]]. | |||
[[Category:Sirius Mods messages]] | [[Category:Sirius Mods messages]] | ||
Revision as of 21:30, 22 April 2014
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.