| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| DFDL serialization issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| catshout |
 Posted: Mon Jan 12, 2015 6:03 am Post subject: DFDL serialization issue |
 |
|
Acolyte
Joined: 15 May 2012
Posts: 57
|
I've a DFDL structure (derived from a Cobol CopyBook) that has been filled by a IIB Map. While trying to serialize the DFDL tree I'm getting a message
"Error code 5832, An error occurred whilst serializing with DFDL, CTDU4035E: Unsupported feature: The IBM DFDL processor cannot assign a default value to a choice group. , /DFDL/ARXAAI6INPUTDATA/ARXAAI_BASE_ACCT_DATA/ARXAAI_OWNING_BRANCH_NBR_X"
The DFDL stanza with this element looks like
| Code: |
<xsd:element dfdl:lengthKind="implicit" name="ARXAAI_OWNING_BRANCH_NBR_X">
<xsd:complexType>
<xsd:sequence>
<xsd:element default="0" dfdl:decimalSigned="no" dfdl:length="9" dfdl:textNumberPattern="000000000+" name="ARXAAI_OWNING_BRANCH_NBR">
<xsd:annotation>
<xsd:documentation>PIC 9(9) display</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="dfdlCobolFmt:PIC9-Display-Zoned__int">
<xsd:minInclusive value="0"/>
<xsd:maxInclusive value="999999999"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element> |
The Local Map stanza for this element looks like
| Code: |
<local>
<input path="."/>
<output path="ARXAAI_OWNING_BRANCH_NBR_X"/>
<convert defaultValue="0">
<input path="BankBranch"/>
<output path="ARXAAI_OWNING_BRANCH_NBR"/>
</convert>
</local> |
Any suggestions what I'd have been missing here? |
|
| Back to top |
|
 |
| kimbert |
| Posted: Mon Jan 12, 2015 6:50 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
The error message is referring to a choice group. There are no choice groups in that DFDL schema. Are you sure that you have quoted the correct part of the DFDL schema?
It's possible that the reported symptom is not the root cause of the problem. If the model is incorrect the parser can stay on its feet for a long time after things have gone wrong. A DFDL Trace ( either from the toolkit's DFDL Debug perspective, or from the runtime via a debug-level user trace ) might be a useful next step.
_________________
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 |
|
|
| catshout |
| Posted: Mon Jan 12, 2015 9:03 am Post subject: |
|
|
Acolyte
Joined: 15 May 2012
Posts: 57
|
Finally I've played around with the stuff and a Trace Node. I've seen that the field inside the sequence hasn't been mapped (neither with the Convert nor with any other Cast Function). An Assign of an explicit value works.
Have opened a PMR for this issue. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Jan 12, 2015 12:13 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I've seen that the field inside the sequence hasn't been mapped (neither with the Convert nor with any other Cast Function). An Assign of an explicit value works. |
Check that the schema used on the left of your map is a correct description of the input data. If the input message tree structure doesn't match that left-hand schema then the Mapping node will not be able to find (some or all of) the input fields.
_________________
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 |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
