| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MXSD issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| mail2me.venky |
 Posted: Fri May 25, 2012 11:37 pm Post subject: MXSD issue |
 |
|
Apprentice
Joined: 11 May 2012
Posts: 26
|
| Code: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="C001E_G_NM_INFO">
<xsd:complexType>
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsStructRep dataElementSeparation="FixedLength"
messageSetDefaultRep="Text1"/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element default="$~\u003ePGN-NAMEINFO\u003c~$"
name="C001E_NM_INFO_L_ID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="18" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="C001E_NM_TYPE_CD" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="2" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="C001E_NM_INFO_LGG_CD" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="2" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="C001E_PTY_NM" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="50" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element default="\u000d\u000a" name="Newline" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="2" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="C001G_G_FSC_NAT">
<xsd:complexType>
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsStructRep dataElementSeparation="FixedLength" messageSetDefaultRep="Text1"/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element default="$~\u003ePGN-FISCLNAT\u003c~$" name="C001G_FSC_NAT_L_ID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="18" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="C001G_G_FSC_NAT">
<xsd:complexType>
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsStructRep dataElementSeparation="FixedLength" messageSetDefaultRep="Text1"/>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element default="$~\u003ePGN-FISCLNAT\u003c~$" name="C001G_FSC_NAT_L_ID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="WMQI_APPINFO">
<tdsElemRep length="18" messageSetDefaultRep="Text1" precision="-1"/>
</xsd:appinfo>
</xsd:annotation>
</xsd:element> |
The above is part of mxsd. i am getting below warnings for all unbounded segments.
Element 'C001E_G_NM_INFO' has unbounded maxOccurs when the enclosing structure has Data Element Separation 'FixedLength'. It must be the last member of the structure. Physical format: 'Text1'.
Element 'C001G_G_FSC_NAT' has unbounded maxOccurs when the enclosing structure has Data Element Separation 'FixedLength'. It must be the last member of the structure. Physical format: 'Text1'.
Can someone help me to solve this warnings? Thanks in advance. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Sat May 26, 2012 3:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
What part of the message do you not understand? It's explicit about what the problem is, and explicit about how to solve it.
Or at least, one way to solve it.
You are modelling a fixed length structure. That means Broker must be able to know exactly how long this structure is going to be. If you have a field that repeats an unlimited number of times and it's in the middle of the record, how is Broker going to know to look for another occurrence of the same field, or to look for the next field?
If you take some time to use [c o d e ] tags, and explain the logical structure of your model, it's possible that someone will offer additional suggestions, other than what the error message has said to do. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat May 26, 2012 8:24 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| You are modelling a fixed length structure. That means Broker must be able to know exactly how long this structure is going to be. If you have a field that repeats an unlimited number of times and it's in the middle of the record, how is Broker going to know to look for another occurrence of the same field, or to look for the next field? |
As I said here
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mail2me.venky |
| Posted: Sat May 26, 2012 8:58 am Post subject: |
|
|
Apprentice
Joined: 11 May 2012
Posts: 26
|
so what should i have to do ?
is there any work around ? any solution procedure |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat May 26, 2012 9:10 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Your model as described is not valid.
You need to change your model.
A simple way to do this will be to delete the elements from the model that are being complained about.
There are several different ways of changing your model so that it is valid.
Not all of them will end up actually parsing your real data.
If you take some time to use [c o d e ] tags, and explain the logical structure of your model, it's possible that someone will offer additional suggestions, other than what the error message has said to do.
You are basically asking for us to tell you how to change your program so that it does the right thing, without telling us in any way what the right thing is. |
|
| 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
|
|
|
|
