| Author |
Message
|
| Ravin |
 Posted: Tue Dec 09, 2014 2:13 pm Post subject: DFDL Fixed Length Parsing Error |
 |
|
Novice
Joined: 18 Nov 2010
Posts: 11
|
Hello All,
I tried to create a simple DFDL message model with 3 fields as Fixed Length.
Below is the schema:
| Code: |
<?xml version="1.0" encoding="UTF-8"?><xsd:schema xmlns:dfdl="http://www.ogf.org/dfdl/dfdl-1.0/" xmlns:ibmDfdlExtn="http://www.ibm.com/dfdl/extensions" xmlns:ibmSchExtn="http://www.ibm.com/schema/extensions" xmlns:recSepFieldsFmt="http://www.ibm.com/dfdl/RecordSeparatedFieldFormat" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://www.ibm.com/dfdl/RecordSeparatedFieldFormat" schemaLocation="IBMdefined/RecordSeparatedFieldFormat.xsd"/>
<xsd:annotation>
<xsd:appinfo source="http://www.ogf.org/dfdl/">
<dfdl:format byteOrder="{$dfdl:byteOrder}" encoding="{$dfdl:encoding}" escapeSchemeRef="recSepFieldsFmt:RecordEscapeScheme" occursCountKind="fixed" ref="recSepFieldsFmt:RecordSeparatedFieldsFormat"/>
</xsd:appinfo>
</xsd:annotation>
<xsd:element ibmSchExtn:docRoot="true" name="myFxLn_msg">
<xsd:complexType>
<xsd:sequence dfdl:separator="%CR;%LF;%WSP*;">
<xsd:element dfdl:initiator="" dfdl:occursCountKind="implicit" maxOccurs="unbounded" name="body">
<xsd:complexType>
<xsd:sequence dfdl:separator="%#44;" dfdl:separatorPolicy="suppressedAtEndLax">
<xsd:element ibmDfdlExtn:sampleValue="body_value1" name="body_elem1" type="xsd:string"/>
<xsd:element ibmDfdlExtn:sampleValue="body_value2" name="body_elem2" type="xsd:string"/>
<xsd:element ibmDfdlExtn:sampleValue="body_value3" name="body_elem3" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema> |
When I select this schema-'myFxLn_msg' in the MQInputnode and provide an input like 'abcabcabc', I get an error - 'DFDL parsing errors have occurred.'
When I enable the mqsichangetrace I get the error description as - 'BIP5807E: The DFDL parser signalled that a processing error occurred. The message from the DFDL parser is: 'CTDP3001E: Root element 'myFxLn_msg' not found in schema.'
Can someone pls. help me with this error..? Thanks a lot.[/code] |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Dec 09, 2014 2:17 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You should be using the DFDL Test Parser in the Toolkit to debug your DFDL models.
It's much easier to use than mqsichangetrace. |
|
| Back to top |
|
|
| Ravin |
| Posted: Tue Dec 09, 2014 2:33 pm Post subject: |
|
|
Novice
Joined: 18 Nov 2010
Posts: 11
|
| I did use the dfdl test parser in the toolkit...and it got parsed successfully. But when I use the dfdl in the mqinput node, the message gets failed to parse... I used mqsichangetrace to get the detailed error message as I was not getting this error information in visual debug... |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Dec 10, 2014 1:51 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
The usual problems are:
- message name is incorrect
- message name is correct but namespace is not specified ( or incorrectly specified )
- schema was not deployed ( or an old version was deployed )
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| Ravin |
| Posted: Wed Dec 10, 2014 9:14 pm Post subject: |
|
|
Novice
Joined: 18 Nov 2010
Posts: 11
|
| Thanks all for the responses...I figured out the issue. It was a deployment issue..missed to include the fixed length xsd. After including all the artifacts it was working fine. Thanks. |
|
| Back to top |
|
|
| Kjakh |
| Posted: Wed Apr 25, 2018 7:39 am Post subject: |
|
|
Newbie
Joined: 24 Apr 2018
Posts: 2
|
I am also facing the same issue in DFDL. My DFDL has one complex type which is having Min occurs as 0 and maxoccurs as 10. its getting parsed successfully in DFDL editor. but when I do the same in MQinput node it fails.
What is Fixed length XSD. please help |
|
| Back to top |
|
|
| timber |
| Posted: Wed Apr 25, 2018 8:09 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| I see nothing to suggest that this is the same issue. Please open a new thread and supply enough detail to allow us to diagnose the problem. So far, the only thing you have told us is 'it fails'. Which falls some way short of a full problem statement. |
|
| Back to top |
|
|
|
|
