DFDL parser messages
- CTDP3000
- Unexpected end of data at byte offset '<insert_0>' while parsing element '<insert_1>'. The parser encountered the end of the data stream or the end of a parent element.
- Severity
- 20 : Error
- Explanation
- While parsing an element, the DFDL parser found that there was not enough data available.
- Response
- Change the DFDL schema so that the length is calculated correctly. Check that previous elements were parsed correctly. Check the message is a valid example.
- CTDP3001
- Root element '<insert_0>' not found in schema.
- Severity
- 20 : Error
- Explanation
- The root element supplied to the DFDL parser was not found in the schema.
- Response
- Check that the correct schema was supplied to the DFDL parser. Check that the name and namespace of the root element are specified correctly. If the element is not a global element, check that the path to the root element is specified correctly.
- CTDP3002
- Unexpected data found at offset '<insert_0>' after parsing completed. Data: '0x<insert_1>...'.
- Severity
- 20 : Error
- Explanation
- This error can be caused by incorrect data or an incorrect model. It is often caused by an inaccurate DFDL model.
- Response
- If the data is correct, check the user trace to determine why parsing has ended prematurely. If the model is correct, remove trailing data from the input data stream.
- CTDP3007
- Element length is set to invalid value of '<insert_0>' on element '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- The DFDL 'length' property contains an expression which has evaluated to an invalid length.
- Response
- Correct the DFDL schema so the DFDL 'length' property contains an expression that will always return a non-negative integer.
- CTDP3011
- Character decoding error. The sequence of bytes starting at byte offset '<insert_0>' is not a valid character in the encoding '<insert_1>' .
- Severity
- 20 : Error
- Explanation
- The bytes supplied to the DFDL parser are not valid for the specified encoding.
- Response
- Check that the encoding has been specified correctly. Note that UTF-8 should not be used when the data is ASCII.
- CTDP3012
- DFDL 'lengthUnits' must not be 'bits' when 'representation' is 'text'.
- Severity
- 20 : Error
- Explanation
- The DFDL specification prohibits this combination of property settings.
- Response
- Correct the DFDL schema.
- CTDP3014
- Internal error: Text encoding is not resolved for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- This is an internal error and should not occur.
- Response
- Report the problem to IBM, supplying the DFDL schema and input data.
- CTDP3016
- Internal error: Unresolved number format for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- This is an internal error and should not occur.
- Response
- Report the problem to IBM, supplying the DFDL schema and input data.
- CTDP3017
- Internal error: Unresolved calendar format for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- This is an internal error and should not occur.
- Response
- Report the problem to IBM, supplying the DFDL schema and input data.
- CTDP3024
- Invalid value '<insert_0>' for Boolean data type.
- Severity
- 20 : Error
- Explanation
- An element of type xs:boolean has a value which does not match the DFDL 'textBooleanTrueRep' or 'textBooleanFalseRep' properties.
- Response
- Correct the input data, or change the DFDL schema so the DFDL properties match the data.
- CTDP3026
- Number '<insert_0>' cannot be parsed.
- Severity
- 20 : Error
- Explanation
- The number value is too large for the logical data type specified for the element.
- Response
- Correct the input data, or change the DFDL schema so that the data type can handle the number value.
- CTDP3027
- Invalid calendar format '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- DFDL property 'calendarPattern' does not contain a valid calendar format.
- Response
- Correct the DFDL schema.
- CTDP3028
- Invalid number format '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- DFDL property 'textNumberPattern' does not contain a valid text number format.
- Response
- Correct the DFDL schema.
- CTDP3029
- Invalid calendar value '<insert_1>' for element '<insert_0>' with '<insert_4>' calendar pattern '<insert_3>'. Parsing failed at offset <insert_2>.
- Severity
- 20 : Error
- Explanation
- The calendar value did not match the calendar pattern for the element.
- Response
- Correct the input data, or change the DFDL schema so that DFDL property 'calendarPatternKind' is 'explicit' and DFDL 'calendarPattern' contains the correct calendar format.
- CTDP3030
- Incorrect binary Boolean value of '<insert_0>' for element '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- An element of type xs:boolean has a value which does not match the DFDL 'binaryBooleanTrueRep' or 'binaryBooleanFalseRep' properties.
- Response
- Correct the input data, or change the DFDL schema so the DFDL properties match the data.
- CTDP3031
- Invalid sign for binary packed number for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- The sign nibble in the value of a binary packed number is not recognized.
- Response
- Correct the input data, or change the DFDL schema so DFDL property 'binaryPackedSignCodes' matches the data.
- CTDP3032
- Invalid time zone offset '<insert_1>' either with seconds part or out of valid range 'GMT-14:00' to 'GMT+14:00' found while parsing element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- A time zone offset was parsed that was out of range or contained a seconds part. This is not allowed in DFDL.
- Response
- Check that the DFDL model is an accurate description of the expected data. Check that the input document is correct.
- CTDP3038
- The value of '<insert_0>' is out of range '<insert_2>' for element '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- The number value is too large for the logical data type specified for the element.
- Response
- Correct the input data, or change the DFDL schema so that the data type can handle the number value.
- CTDP3039
- The DFDL parser cannot convert the character value '<insert_0>' into a decimal value.
- Severity
- 20 : Error
- Explanation
- A character value was specified in a DFDL setVariable call, but it could not be converted into a decimal value.
- Response
- Check that the character value specified represents a valid decimal value. Correct the character value.
- CTDP3041
- Initiator '<insert_0>' not found at offset '<insert_1>' for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- One of the expected initiators was not found while parsing an element.
- Response
- Check that the DFDL schema is correct and that the input document contains the correct initiator.
- CTDP3042
- Terminator '<insert_0>' not found at offset '<insert_1>' for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- One of the expected terminators was not found while parsing an element.
- Response
- Check that the DFDL schema is correct and that the input document contains the correct terminator. If this is the final terminator in the message then this error can be avoided by setting property 'documentFinalTerminatorCanBeMissing' to 'yes'.
- CTDP3043
- Text to number conversion error for value '<insert_0>'. Character '<insert_1>' at offset '<insert_2>' cannot be parsed.
- Severity
- 20 : Error
- Explanation
- An error occurred creating a logical number from an input text number value.
- Response
- Correct the input data, or change the DFDL schema so the DFDL properties match the data.
- CTDP3044
- Internal error: Missing binary number format for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- This is an internal error and should not occur.
- Response
- Report the problem to IBM, supplying the DFDL schema and input data.
- CTDP3045
- Internal error: Missing binary Boolean format for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- This is an internal error and should not occur.
- Response
- Report the problem to IBM, supplying the DFDL schema and input data.
- CTDP3051
- Text to number conversion error for value '<insert_0>' for element '<insert_1>': <insert_2>
- Severity
- 20 : Error
- Explanation
- An error occurred creating a logical number from an input text number value.
- Response
- Correct the input data, or change the DFDL schema so the DFDL properties match the data.
- CTDP3052
- Character '<insert_0>' in value '<insert_1>' is invalid for zoned decimal representation of '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- An error occurred creating a logical number from an input zoned number value.
- Response
- Correct the input data, or change the DFDL schema so the DFDL properties match the data.
- CTDP3053
- Zoned text to number conversion error for element '<insert_0>': <insert_1>
- Severity
- 20 : Error
- Explanation
- An error occurred creating a logical number from an input zoned number value.
- Response
- Correct the input data, or change the DFDL schema so the DFDL properties match the data.
- CTDP3054
- Invalid binary number representation for decimal data type for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- The value of DFDL property 'binaryNumberRep' was not valid.
- Response
- Correct the DFDL schema.
- CTDP3055
- Invalid floating point type for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- The value of DFDL property 'binaryFloatRep' was not valid.
- Response
- Correct the DFDL schema.
- CTDP3056
- Illegal substring operation on value '<insert_0>' of element '<insert_1>': <insert_2>
- Severity
- 20 : Error
- Explanation
- An error occurred creating a logical calendar from an input text calendar value.
- Response
- Correct the input data, or change the DFDL schema so the DFDL properties match the data.
- CTDP3057
- No more input data available within the scope of parent element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- While parsing an element within a bounded parent, not enough data was found for the element.
- Response
- Correct the input data, or change the DFDL schema so the DFDL properties match the data.
- CTDP3058
- Separator '<insert_0>' not found at offset '<insert_1>' for sequence within element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- One of the expected separators was not found while parsing a sequence within a complex element.
- Response
- Check that the schema is correct and that the input document contains the correct separator.
- CTDP3059
- Element '<insert_0>' has minOccurs='<insert_2>' and no default value but the input document contained only '<insert_1>' occurrences.
- Severity
- 20 : Error
- Explanation
- The input document contained too few occurrences of the element and it has no default value that can be used for the empty occurrences.
- Response
- Check that the minOccurs value is correct. Check that the input data is correct. If both are correct, specify a default value for the element.
- CTDP3060
- Initiator '<insert_0>' not found at offset '<insert_1>' for sequence or choice within element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- One of the expected initiators was not found while parsing a sequence or choice within a complex element.
- Response
- Check that the schema is correct and that the input document contains the correct initiator.
- CTDP3061
- Terminator '<insert_0>' not found at offset '<insert_1>' for sequence or choice within element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- One of the expected terminators was not found while parsing a sequence or choice within a complex element.
- Response
- Check that the schema is correct and that the input document contains the correct terminator. If this is the final terminator in the message then this error can be avoided by setting property 'documentFinalTerminatorCanBeMissing' to 'yes'.
- CTDP3062
- An unexpected non-postfix separator '<insert_2>' occurs in a postfix position at offset '<insert_1>' in '<insert_3>' group contained within element '<insert_0>', xpath: '<insert_4>'.
- Severity
- 20 : Error
- Explanation
- The element is the final element in its parent group. The 'separatorPosition' setting on the parent group is not 'postfix'. No separator should appear after this element.
- Response
- Change the 'separatorPosition' of the parent group to 'postfix', or correct the input document to remove the separator.
- CTDP3063
- Parser setup warning. No document handler was supplied.
- Severity
- 20 : Error
- Explanation
- Set up a document handler before the parseSetup() method is called. A default document handler will be used, and it will log the events to the console.
- Response
- If you do not want to use the default document handler, use the setDocumentHandler() method to install a document handler.
- CTDP3064
- Parser setup error. No valid DFDL Grammar was supplied.
- Severity
- 20 : Error
- Explanation
- No valid DFDL Grammar was supplied before starting a parse or setting a variable.
- Response
- Call the setGrammar() method supplying a valid DFDL Grammar before starting a parse or setting variables.
- CTDP3065
- Parser setup error. No input document was supplied.
- Severity
- 20 : Error
- Explanation
- No input document was supplied before calling parseSetup.
- Response
- Call the setInputDocument() or setBufferHandler() method before calling parseSetup().
- CTDP3066
- Parser setup error. Input data was specified incorrectly.
- Severity
- 20 : Error
- Explanation
- The input document was specified using both setInputDocument() and setBufferHandler().
- Response
- Call either setInputDocument() or setBufferHandler(), but not both methods.
- CTDP3067
- Parser setup error. No root element was specified.
- Severity
- 20 : Error
- Explanation
- No root element was specified before parseSetup was called.
- Response
- Call setRootElement() before calling parseSetup().
- CTDN3069
- Value '<insert_0>' is not facet-valid with respect to minLength '<insert_1>' for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- Element value does not comply with the XML Schema minLength facet. This has been reported because schema validation is enabled.
- Response
- Correct the input data.
- CTDN3070
- Value '<insert_0>' is not facet-valid with respect to maxLength '<insert_1>' for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- Element value does not comply with the XML Schema maxLength facet. This has been reported because schema validation is enabled.
- Response
- Correct the input data.
- CTDN3071
- Value '<insert_0>' is not facet-valid with respect to pattern for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- Element value does not comply with the XML Schema pattern facets. This has been reported because schema validation is enabled.
- Response
- Correct the input data.
- CTDN3072
- Value '<insert_0>' is not facet-valid with respect to minInclusive '<insert_1>' for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- Element value does not comply with the XML Schema minInclusive facet. This has been reported because schema validation is enabled.
- Response
- Correct the input data.
- CTDN3073
- Value '<insert_0>' is not facet-valid with respect to maxInclusive '<insert_1>' for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- Element value does not comply with the XML Schema maxInclusive facet. This has been reported because schema validation is enabled.
- Response
- Correct the input data.
- CTDN3074
- Value '<insert_0>' is not facet-valid with respect to minExclusive '<insert_1>' for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- Element value does not comply with the XML Schema minExclusive facet. This has been reported because schema validation is enabled.
- Response
- Correct the input data.
- CTDN3075
- Value '<insert_0>' is not facet-valid with respect to maxExclusive '<insert_1>' for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- Element value does not comply with the XML Schema maxExclusive facet. This has been reported because schema validation is enabled.
- Response
- Correct the input data.
- CTDN3076
- Value '<insert_0>' is not facet-valid with respect to enumeration for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- Element value does not comply with the XML Schema enumeration facets. This has been reported because schema validation is enabled.
- Response
- Correct the input data.
- CTDN3077
- Value '<insert_0>' is not facet-valid with respect to totalDigits '<insert_1>' for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- Element value does not comply with the XML Schema totalDigits facet. This has been reported because schema validation is enabled.
- Response
- Correct the input data.
- CTDN3078
- Value '<insert_0>' is not facet-valid with respect to fractionalDigits '<insert_1>' for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- Element value does not comply with the XML Schema fractionalDigits facet. This has been reported because schema validation is enabled.
- Response
- Correct the input data.
- CTDN3079
- Value '<insert_0>' is not facet-valid with respect to length '<insert_1>' for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- Element value does not comply with the XML Schema length facet. This has been reported because schema validation is enabled.
- Response
- Correct the input data.
- CTDP3080
- The specified feature '<insert_0>' is not recognized.
- Severity
- 20 : Error
- Explanation
- The DFDL feature passed to getFeature() or setFeature() was not recognized.
- Response
- Ensure that a valid DFDL feature is specified.
- CTDP3082
- The binary float representation '<insert_0>' on element '<insert_1>' is not a valid value for this property.
- Severity
- 20 : Error
- Explanation
- The value of DFDL property 'binaryFloatRep' was not valid.
- Response
- Correct the DFDL schema. If 'binaryFloatRep' contains an expression ensure that it always returns a valid value.
- CTDP3083
- Invalid value '0x<insert_1>' for element '<insert_0>' with binary representation '<insert_2>' : nibble value '<insert_3>' is not valid at position '<insert_4>' for this packed format.
- Severity
- 20 : Error
- Explanation
- The parser was unable to parse the packed binary number value as it contained an invalid nibble at the indicated position.
- Response
- Check the DFDL properties 'binaryNumberRep' , 'byteOrder' and if applicable 'binaryPackedSignCodes' for this element are correct.
- CTDP3084
- Element '<insert_0>' has maxOccurs='1' but the input document contained more than one occurrence.
- Severity
- 20 : Error
- Explanation
- The input document contained too many occurrences of the element.
- Response
- Check that the maxOccurs value is correct. Check that the input data is correct.
- CTDP3085
- Cannot resolve expression '<insert_2>' for DFDL property '<insert_1>' defined on object '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- An expression which was syntactically correct, could not be evaluated at runtime.
- Response
- Examine user trace to diagnose why the expression could not be evaluated. Check that any path locations in the expression resolve to elements in the message before "<insert_0>".
- CTDN3086
- Value '<insert_0>' is not facet-valid with respect to the union of restrictions for element '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- The element is defined by a union of simple types. None of the simple types successfully validate the value. This has been reported because schema validation is enabled.
- Response
- Correct the input data.
- CTDN3087
- Element '<insert_0>' has maxOccurs '<insert_1>' but the input document contained '<insert_2>' occurrences.
- Severity
- 20 : Error
- Explanation
- The DFDL parser received too many occurrences of the element. This has been reported because schema validation is enabled.
- Response
- Check that the DFDL model is an accurate description of the expected info set. If the model is correct, the supplied input document must be incorrect.
- CTDN3088
- Element '<insert_0>' has minOccurs '<insert_1>' and no default value, but the input document has only '<insert_2>' occurrences.
- Severity
- 20 : Error
- Explanation
- The input document has too few occurrences of the element and it has no default value that can be used for the missing occurrences. This has been reported because schema validation is enabled.
- Response
- Check that the DFDL model is an accurate description of the expected info set. Check that the input document is correct. If both are correct, specify a default value for the element.
- CTDP3095
- The value '<insert_3>' of the external variable with Name '<insert_0>' and Namespace '<insert_1>' is out of range.
- Severity
- 20 : Error
- Explanation
- A call was made to the setVariable() method on the DFDL Parser. The value provided is out of the range of the type of the variable.
- Response
- Correct the call so that the value is within range.
- CTDP3096
- External variable with Name '<insert_0>' and Namespace '<insert_1>' cannot be created with value of '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- A call was made to the setVariable() method on the DFDL Parser. The value provided could not be used to create the variable.
- Response
- Correct the call so that the value conforms to the type of the variable.
- CTDP3097
- The value of variable '<insert_0>' is not valid for the type of the variable. Variable namespace: '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- The defineVariable annotation for variable '<insert_0>' has a defaultValue attribute. The default value expression returned a value that is not valid for the type of this variable.
- Response
- Change the DFDL schema to correct the default value expression or change the type of the variable.
- CTDP3098
- Cannot set the external DFDL variable because no global variable with the specified Name '<insert_0>' and Namespace '<insert_1>' is defined.
- Severity
- 20 : Error
- Explanation
- A call was made to the setVariable() method on the DFDL Parser. The supplied variable name was not valid.
- Response
- Correct the call so that the variable name is correct. Check that the correct schema has been supplied to the DFDL processor before making the setVariable call.
- CTDP3099
- Parsed value of '<insert_0>' for element '<insert_1>' is out of range for the data type.
- Severity
- 20 : Error
- Explanation
- The text number value is too large for the logical data type specified for the element.
- Response
- Correct the input data or change the DFDL schema so that the data type can handle the number value.
- CTDP3102
- Invalid DFDL exponent character in the number format (length > 1): <insert_0>.
- Severity
- 20 : Error
- Explanation
- DFDL property 'textStandardExponentRep' must resolve to a single character. This is an IBM DFDL restriction.
- Response
- Correct the DFDL schema.
- CTDP3104
- None of the branches of the choice group under element '<insert_0>' were found in the input data at offset '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- The DFDL parser parsed a choice group, but none of the members of the choice group were parsed successfully.
- Response
- Take a user trace. Check that the input data was parsed correctly before the choice group was encountered. Read the user trace to determine why none of the branches were parsed successfully.
- CTDP3105
- The variable cannot be set because it is not defined as an external variable. Name '<insert_0>' and Namespace '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- A call was made to the setVariable() method on the DFDL Parser. The defineVariable annotation for the variable does not have the 'external' attribute set to 'true'.
- Response
- Correct the DFDL schema.
- CTDP3107
- A DFDL assert with condition '<insert_3>' evaluated to false with message '<insert_2>' during parsing of '<insert_0>' at offset '<insert_1>' in the data stream.
- Severity
- 20 : Error
- Explanation
- The component quoted in the message has a DFDL assert that evaluated to false. The data is not valid according to the rule in the DFDL assert.
- Response
- Investigate why the condition evaluated to false.
- CTDP3108
- When parsing, the IBM DFDL processor does not support an empty or missing element with a default value.
- Severity
- 20 : Error
- Explanation
- The DFDL parser found an empty or missing element, and the element has a default value. This is an IBM DFDL restriction.
- Response
- Correct the input data to provide a value for the element, or change the DFDL schema so the element is optional with 'minOccurs' of '0' or is nillable with 'nilLiteralValue' of '%ES;'.
- CTDP3109
- A DFDL discriminator with condition '<insert_3>' evaluated to false with message '<insert_2>' during parsing of '<insert_0>' at offset '<insert_1>' in the data stream.
- Severity
- 20 : Error
- Explanation
- The point of uncertainty on the parent component has not been resolved. If there is a processing error, the DFDL parser will backtrack to the parent component and try another path through the model.
- Response
- No user action is required.
- CTDP3110
- The DFDL parser has backtracked after a processing error. Parsing will resume at position '<insert_0>' offset '<insert_1>' in the data stream.
- Severity
- 20 : Error
- Explanation
- A processing error occurred while the DFDL parser was trying to resolve a point of uncertainty. The DFDL parser has returned to the point of uncertainty and will now try to parse the next available path.
- Response
- No user action is required.
- CTDP3111
- The expression '<insert_0>' in a DFDL assert could not be evaluated during parsing of '<insert_1>' at offset '<insert_2>' in the data stream.
- Severity
- 20 : Error
- Explanation
- The DFDL expression in the DFDL assert could not be evaluated.
- Response
- Check that all variables are in scope, and that all elements referenced by the expression have already been parsed.
- CTDP3113
- The expression '<insert_0>' in a DFDL discriminator could not be evaluated during parsing of '<insert_1>' at offset '<insert_2>' in the data stream.
- Severity
- 20 : Error
- Explanation
- The DFDL expression in the DFDL discriminator could not be evaluated.
- Response
- Check that all variables are in scope, and that all elements referenced by the expression have already been parsed.
- CTDP3115
- Calendar object cannot be created from an empty string for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- The parser is unable to create a Calendar object because the parsed value for the element was a zero-length string.
- Response
- Correct the input data to provide a value, or change the DFDL schema so the element is optional with 'minOccurs' of '0' or is nillable with 'nilLiteralValue' of '%ES;'.
- CTDP3116
- Number cannot be created from an empty string for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- The parser is unable to create a Number object because the parsed value for the element was a zero-length string.
- Response
- Correct the input data to provide a value, or change the DFDL schema so the element is optional with 'minOccurs' of '0' or is nillable with 'nilLiteralValue' of '%ES;'.
- CTDP3117
- Internal error: a null string was provided for a text conversion routine for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- This is an internal error and should not occur.
- Response
- Report the problem to IBM, supplying the DFDL schema and input data.
- CTDP3119
- Internal error: invalid length units for binary representation for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- This is an internal error and should not occur.
- Response
- Report the problem to IBM, supplying the DFDL schema and input data.
- CTDP3121
- Negative value of '<insert_0>' cannot be assigned to an unsigned decimal data type for element '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- The element has DFDL property 'decimalSigned' set to 'no' but the parsed value for the element is negative.
- Response
- Correct the input data, or change the DFDL schema so 'decimalSigned' is 'yes'.
- CTDP3122
- Invalid encoding name '<insert_1>' specified for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- The DFDL property 'encoding' does not have a recognized encoding value.
- Response
- Change the DFDL schema or the setVariable call so the encoding is correct for the input data.
- CTDP3123
- Prefixed length for element '<insert_0>' is negative value of '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- An element has DFDL property 'lengthKind' set to 'prefixed' but the parsed value for the prefix length was negative.
- Response
- Correct the input data.
- CTDP3124
- Prefixed length for element '<insert_0>' cannot be resolved.
- Severity
- 20 : Error
- Explanation
- An element has DFDL property 'lengthKind' set to 'prefixed' but the parser was unable to parse a value for the prefix length.
- Response
- Correct the input data, or change the DFDL schema so the prefix length simple type for the element is correctly modelled.
- CTDP3125
- Invalid value for 'inputValueCalc' for element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- The value returned by the DFDL property 'inputValueCalc' expression does not match the type of the element.
- Response
- Change the DFDL schema to correct the 'inputValueCalc' expression or the type for the element.
- CTDP3128
- The DFDL parser could not read the value of element '<insert_1>' at offset '<insert_0>'. The length of the element is '<insert_2>' in units of '<insert_3>' but there is not enough data in the data stream.
- Severity
- 20 : Error
- Explanation
- While parsing an element, the DFDL parser found that insufficient data remains in the data stream.
- Response
- Change the DFDL schema so that the length is calculated correctly. Check that previous elements were parsed correctly.
- CTDP3129
- DFDL property 'lengthKind' must be set. Element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- DFDL 1.0 specification requires that every element has a value set for 'lengthKind'.
- Response
- Correct the DFDL schema.
- CTDP3131
- XPath expression '<insert_0>' for 'inputValueCalc' for element '<insert_1>' returned a null value.
- Severity
- 20 : Error
- Explanation
- The parser was not able to evaluate the DFDL property 'inputValueCalc' expression for the element.
- Response
- Change the DFDL schema to correct the 'inputValueCalc' expression for the element.
- CTDP3133
- An unexpected terminator was found for an empty element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- The element is empty. The DFDL property 'emptyValueDelimiterPolicy' specifies that the element should not have a terminator when it is empty.
- Response
- Either the data stream is incorrect or the schema is incorrect. Remove the unexpected terminator from the data stream, or set 'emptyValueDelimiterPolicy' to 'both' or 'terminator'.
- CTDP3134
- Terminator was not found for an empty element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- The element is empty. The DFDL property 'emptyValueDelimiterPolicy' specifies that the element should have a terminator when it is empty.
- Response
- Either the data stream is incorrect or the schema is incorrect. Add the terminator to the data stream or set 'emptyValueDelimiterPolicy' to 'none' or 'initiator'.
- CTDN3135
- The value of element '<insert_1>' did not match the value of its XSDL 'fixed' attribute.
- Severity
- 20 : Error
- Explanation
- The element has a 'fixed' attribute in the schema. The value of the element must match the value of this attribute. This has been reported because schema validation is enabled.
- Response
- Change the DFDL schema to correct or remove the 'fixed' attribute, or correct the input data.
- CTDP3136
- An unexpected terminator was found for a nil element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- The element is nil. The DFDL property 'nilValueDelimiterPolicy' specifies that the element should not have a terminator when it is nil.
- Response
- Either data stream is incorrect or the schema is incorrect. Remove the unexpected terminator from the data stream, or set 'nilValueDelimiterPolicy' to 'both' or 'terminator'.
- CTDP3137
- Terminator was not found for a nil element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- The element is nil. The DFDL property 'nilValueDelimiterPolicy' specifies that the element should have a terminator when it is nil.
- Response
- Either the data stream is incorrect or the schema is incorrect. Add the terminator to the data stream, or set 'nilValueDelimiterPolicy' to 'none' or 'initiator'.
- CTDP3138
- An unexpected initiator was found for an empty element '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- The element is empty. The DFDL property 'emptyValueDelimiterPolicy' specifies that the element should not have a initiator when it is empty.
- Response
- Either data stream is incorrect or the schema is incorrect. Remove the unexpected initiator from the data stream or set 'emptyValueDelimiterPolicy' to 'both' or 'initiator'.
- CTDP3139
- The DFDL parser cannot apply pad byte to element '<insert_0>', due to combination of 'lengthUnits' set to 'characters' and a variable-width encoding.
- Severity
- 20 : Error
- Explanation
- When 'lengthUnits' is 'characters' and a byte value is specified for the pad character, the encoding must be fixed width.
- Response
- Correct the DFDL schema, or ensure that a fixed width encoding is supplied for the data.
- CTDP3141
- Invalid value found for DFDL 'byteOrder' property '<insert_1>' defined on element '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- The DFDL property 'byteOrder' does not have a recognized value.
- Response
- Change the DFDL schema or the setVariable call so the byte order is correct for the input data.
- CTDP3142
- Negative value of '<insert_0>' cannot be assigned to the unsigned data type '<insert_1>' for element '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- The element has an unsigned data type but the parsed value for the element is negative.
- Response
- Correct the input data, or change the DFDL schema so the data type is signed.
- CTDP3143
- The DFDL parser could not parse the DFDL 'binaryCalendarEpoch' property value of '<insert_0>' while parsing element '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- DFDL property 'binaryCalendarEpoch' must be a valid dateTime value.
- Response
- Correct the DFDL schema.
- CTDP3144
- Unexpected end of input document at byte offset '<insert_0>' while parsing <insert_2> group '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- While parsing a group, the DFDL parser found that there was not enough data remaining in data stream.
- Response
- Change the DFDL schema so that the length is calculated correctly. Check that previous elements were parsed correctly.
- CTDP3145
- The DFDL parser cannot apply nil literal byte '<insert_2>' to element '<insert_0>', due to combination of 'lengthUnits' set to 'characters' and a variable-width encoding '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- When 'lengthUnits' is 'characters' and a byte value is specified for 'nilLiteralValue', the encoding must be fixed width.
- Response
- Correct the DFDL schema, or ensure that a fixed width encoding is supplied for the data.
- CTDP3146
- The DFDL parser could not parse element '<insert_0>'. The DFDL property 'escapeKind' is set to 'escapeBlock', but the 'escapeBlockEnd' property value '<insert_1>' was not matched before the end of the data stream or the end of a parent element.
- Severity
- 20 : Error
- Explanation
- While parsing an element, the DFDL parser could not find the end of an escape block. When the DFDL property 'escapeKind' is set to 'escapeBlock', an escape block started by matching the property 'escapeBlockStart' must be terminated by matching the property 'escapeBlockEnd'.
- Response
- Either the data stream is incorrect or the schema is incorrect. Add the end of the escape block to the data stream, or modify the 'escapeBlockEnd' property to correctly match the end of the escape block.
- CTDP3147
- Parser state error. Cannot call '<insert_0>' while a parse is in progress.
- Severity
- 20 : Error
- Explanation
- Cannot change the parser configuration while a parse is in progress.
- Response
- Complete the current parse or call 'resetParser' before altering the parser configuration.
- CTDP3148
- Infinite loop at offset <insert_1>: The DFDL parser cannot process array element '<insert_0>' because maxOccurs is 'unbounded' and the length of the previous occurrence was zero.
- Severity
- 20 : Error
- Explanation
- The parser cannot process this data stream using the schema provided because it would cause the program to enter an infinite loop.
- Response
- Correct the DFDL schema so that the parser moves forward while processing every occurrence of this element. If the parent sequence has a separator and 'separatorSuppressionPolicy' is 'anyEmpty' then consider whether 'trailingEmpty' would be a better choice.
- CTDP3149
- Error reading data from the input document : '<insert_0>'.
- Severity
- 20 : Error
- Explanation
- The parser received an unexpected error reading data from the input document or stream.
- Response
- Fix the problem and re-parse.
- CTDP3150
- The DFDL parser cannot read the value of element '<insert_0>' because it has a length of '<insert_1>' digits. DFDL Parser only parses binary numbers up to length '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- The DFDL Parser cannot parse elements of a type based on decimal that are longer than the indicated limit. This is an IBM DFDL limitation.
- Response
- Modify the DFDL schema such that the element length is within the length limit.
- CTDP3151
- The DFDL parser could not find the value of element '<insert_0>' with lengthKind 'pattern' at offset '<insert_1>' because the pattern failed to match.
- Severity
- 20 : Error
- Explanation
- An element has a lengthKind of 'pattern'. The DFDL Parser attempted to match the data but a match could not be found.
- Response
- Ensure that the pattern used matches the input data supplied to the parser.
- CTDP3152
- The DFDL parser exceeded the allowed time limit for matching element '<insert_0>' with lengthKind 'pattern' and lengthPattern '<insert_1>'.
- Severity
- 20 : Error
- Explanation
- The DFDL parser sets a time limit for finding a match when parsing an element with lengthKind 'pattern'. The limit has been exceeded while attempting to match element '<insert_0>' using the pattern '<insert_1>'.
- Response
- Check that the pattern and the data does not cause an infinite loop.
- CTDP3153
- The DFDL parser caused an unexpected error while matching element '<insert_0>' with lengthKind 'pattern' and lengthPattern '<insert_1>'. The error code was '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- The DFDL parser attempted to match the element using the pattern, but the pattern matching engine returned the indicated error code.
- Response
- Check that the pattern is suitable for matching the element from the input data.
- CTDP3154
- The DFDL parser caused an unexpected error while matching element '<insert_0>' with lengthKind 'pattern'. The lengthPattern could not be used.
- Severity
- 20 : Error
- Explanation
- The DFDL parser attempted to match the element using a pattern, but the pattern could not be used.
- Response
- Check that the pattern is suitable for matching the element from the input data.
- CTDP3155
- The DFDL parser reached a character limit of '<insert_1>' characters for element '<insert_0>' with lengthKind 'pattern'. The pattern failed to match.
- Severity
- 20 : Error
- Explanation
- The DFDL parser attempted to match the element using a pattern, but reached the maximum character limit. The pattern failed to match the available data.
- Response
- Adjust the DFDL schema so that the content of the element is modelled.
- CTDP3156
- The string literal '<insert_0>' contains characters which are not valid in the encoding '<insert_1>' .
- Severity
- 20 : Error
- Explanation
- The string literal is not valid for the specified encoding.
- Response
- Check that the encoding has been specified correctly.
- CTDP3157
- The DFDL parser reached a character limit of '<insert_1>' characters for element '<insert_0>' with lengthKind 'pattern'. The pattern matched the available data but expected more data.
- Severity
- 20 : Error
- Explanation
- The DFDL parser attempted to match the element using a pattern, but reached the maximum character limit. The pattern successfully matched the available data, but may have matched more data if it had been available.
- Response
- Adjust the DFDL schema so that the content of the element is modelled.
- CTDP3158
- The DFDL parser cannot read the value of element '<insert_0>' because it has a length of '<insert_1>' bits. DFDL Parser only parses binary numbers up to a maximum representation length '<insert_2>' bits.
- Severity
- 20 : Error
- Explanation
- The DFDL Parser cannot parse elements that are longer than the indicated limit. This is an IBM DFDL limitation.
- Response
- Modify the DFDL schema such that the element length is within the limit.
- CTDP3159
- The expression '<insert_0>' for the 'choiceDispatchKey' property resolved to an empty string on choice group '<insert_1>' .
- Severity
- 20 : Error
- Explanation
- The DFDL parser parsed a choice group but the 'choiceDispatchKey' resolved to an empty string.
- Response
- Correct the expression used for the 'choiceDispatchKey' and ensure it can resolve to a string literal for the message being parsed.
- CTDP3160
- The expression '<insert_0>' for the 'choiceDispatchKey' property resolved to the value '<insert_1>' but failed to match the 'choiceBranchKey' of any of the branches in choice group '<insert_2>'.
- Severity
- 20 : Error
- Explanation
- The DFDL parser parsed a choice group but the 'choiceDispatchKey' doesn't match the 'choiceBranchKey' of any of the choice group's children.
- Response
- Correct the expression used for the 'choiceDispatchKey' and ensure it resolves to a string literal that matches one of the 'choiceBranchKey' values in scope.
- CTDP3161
- The expression '<insert_0>' for the 'choiceDispatchKey' property failed to resolve to a value of type string on choice group '<insert_1>'. The expression resolved to the value '<insert_2>' of type '<insert_3>'.
- Severity
- 20 : Error
- Explanation
- The DFDL parser parsed a choice group but the 'choiceDispatchKey' doesn't resolve to a value of type string.
- Response
- Correct the expression used for the 'choiceDispatchKey' and ensure it resolves to a value of type string that matches one of the 'choiceBranchKey' values in scope.
- CTDP3162
- The DFDL parser cannot read the value of element '<insert_0>' of type '<insert_1>' because it has DFDL 'length' property '<insert_2>' with DFDL 'lengthUnits' property '<insert_3>'. The length of the data exceeds the capacity of the element type.
- Severity
- 20 : Error
- Explanation
- The DFDL Parser cannot parse elements with a length that exceeds the capacity of the type of the element.
- Response
- Modify the DFDL schema such that the element length is within the limit of the capacity of the type.