In order to cover a wide variety of situations, error messages typically have more than one parameter. Each parameter points to either field names or field positions. The following table lists all possible error conditions. At run-time, the parameters in braces ({}) are filled in with context-specific data.
Error Code |
Description |
---|---|
YIF_OVERLAPPING |
Field {0} intersects Field {1} in Record {2} This error code indicates that two fields in the same record have overlapping positions |
YIF_INVALID_ |
Field {0} has invalid bounds: startPos={1} endPos={2} This error code indicates that the startPosition of a field is greater than the end position of the field |
YIF_INVALID_ |
The position of the record type field is invalid. |
YIF_EMPTY_ |
Record {0} does not have a record type identifier. When the data contains a record whose record type has not been declared in the schema. |
YIF_EMPTY_ |
No fields exist to match for a record. The data contains a record with a record type identifier but the individual fields do not exist |
YIF_INVALID_ |
Record {0} should not have a gap [Field {1} endPosition={2}] and [Field {3} startPosition={4}]. n a positional format, two fields should not have a gap. It is fixed width, so unaccounted gaps cannot exist. Fixed width. Period. |
YIF_FIELD_ |
In Record {0}, the field {1}[startPos={2}, endPos={3}] overlaps record type field {4} [startPos={5}]. In a positional format, when a field datum overlaps with the boundary of a record type identifier. |
YIF_FIELD_ |
In Record {0}, the field {1}[position={2}] overlaps record type field {3} [position={4}]. In a delimited format, when a field datum overlaps with the boundary of a record type identifier |
YIF_SCHEMA_ |
Schema contains a cycle starting at element: {0} and ending before element: {1}. The schema description does not allow for cyclical containment. If it does, the above error code is reported. |
YIF_RECORD_ |
Record Id {0} is too large. Record Identifiers have a fixed width, this error is reported when the size is exceeded. |
YIF_FIELD_ |
Field {0} in attribute map does not exist in record {1}. When translating from XML to positional/delimited format, if the field that an XML attribute maps to does not exist. |
YIF_TOO_ |
Number of attribute maps = {0} in elementMap {1} exceeds the number of fields = {2} in record {3}. The number of attributes in an XML element that need to be mapped to fields, cannot exceed the number of fields in the corresponding record. |
YIF_INVALID_ |
RecordIdStartPos: {0} must be less than the RecordIdEndPos: {1}. In a positional format, the bounds of the record identifier must be correct. |
YIF_RECORD_ |
Could not match record id: {0} with any record declared in the schema |
YIF_INCORRECT_ |
Record length is incorrect. |
YIF_RECORD_ |
Too few fields. Min fields = {0} Found = {1} |
YIF_TOO_FEW |
Found few fields for record id: {0}. Expected = {1} Found = {2} |
YIF_TOO_MANY |
Too many fields for record id: {0}. Expected = {1} Found = {2} |
YIF_RECORD_ |
Too many fields. Max fields = {0} Found = {1} |
YIF_RECORD_TOKEN |
Scanned record name: {0} is not fully matched. Current Token: {1} |
YIF_INCOMPLETE |
Record Set preceding scanned record name: {0} is not completely matched. |
YIF_MAX_ |
Number of matches exceeds Max matches for record: {0} |
YIF_FILE_ |
File length: {0} must exceed the sum of the fileHeaderLength:{1} and the fileTrailerLength: {2} |
YIF_FILE_ |
Expected file header id: {0} is not found |
YIF_FILE_TRAILER_ |
Expected file trailer id: {0} is not found |
YIF_FILE_HEADER |
Expected file header id: <{0}> does not match found: <{1}> |
YIF_FILE_TRAILER |
Expected file trailer id: <{0}> does not match found: <{1}> |
YIF_UNABLE_ |
Unable to set the bounds on input stream ScanLength= <{0}> ScanStartPosition=<{1}> |
YIF_DIR_DOES |
The specified directory: {0} does not exist. |
YIF_DIR_IS_ |
The specified directory: {0} does not have write permissions. |
YIF_INVALID_INCLUDES_PATTERN |
The includes pattern: {0} is not a valid regular expression. |