| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TDS Messsage Definition Problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| satya2481 |
 Posted: Wed Dec 05, 2007 12:38 am Post subject: TDS Messsage Definition Problem |
 |
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Hi All,
I have a requirement to define a TDS message set. A sample message should look like
101Field1Field2
102Field3Field4
102Field3Field4
---------------
---------------
102Field3Field4
The structure of the message is
Response
RecordType
Field1
Field2
Coverage
RecordType
Field3
Field4
Here Response is the main header
Response.RecordType should be 101
Response.Coverage.RecordType should be 102
Coverage is a complex element and can repeat 1 to N
If I create Response and Coverage complex elements as separate segments then I am able to produce the required ouput. But Coverage should be under Response segment. I tried using <CR><LF> as a delimiter, as a group indicator etc but was not able to generate the required output message.
I need some help on this issue.
Thanks in advance
SSM
_________________
IBM Certified Solution Developer WebSphere Message Broker V6.0
IBM Certified System Administrator WebSphere MQ V6.0 |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Dec 05, 2007 1:37 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Good try. Your message structure is not indented ( you should have used the code tag ) but I think I can work out what you are trying to do. The following model is not tested, so let me know if it doesn't work ( after taking a user trace and reading it carefully )
- '101' and '102' are tags, not data fields. So you should be using Tagged Fixed Length.
- Coverage is a child of RecordType. So RecordType also needs to be Tagged Fixed Length.
- Don't forget to set minOccurs=0, maxOccurs=-1 on Coverage
| Code: |
ResponseMessage [ DES=Tagged Fixed Length, Tag Length=3 ]
RecordType [ Tag='102', DES=Tagged Fixed Length, Tag Length=3 ]
Field1
Field2
Coverage [ minOccurs=0, maxOccurs=-1 ]
RecordType
Field3
Field4
|
|
|
| Back to top |
|
|
| satya2481 |
| Posted: Thu Dec 06, 2007 6:54 am Post subject: |
|
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Hi Kimbert,
Thanks for your reply,
Well I resolved the issue by constructing the message set as indicated below.
| Code: |
ResponseMessage {Variable Length Elements delimited, Delimiter is <CR><LF>}
Response {Complex element, Fixed length MinOcc = 1 MaxOccu = 1}
RecordType {Simple element and length specified}
Field1 {Simple element and length specified}
Field2 {Simple element and length specified}
CoverageCode {Fixed Length GroupIndicator as <CR><LF>, MinOccu = 1 MaxOccu = -1}
Field3 {Simple element and length specified}
Field4 {Simple element and length specified}
|
But still not sure how it worked !!!
_________________
IBM Certified Solution Developer WebSphere Message Broker V6.0
IBM Certified System Administrator WebSphere MQ V6.0 |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Dec 06, 2007 7:23 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
So you decided to treat your tags as data.
That's OK, as long as you are absolutely certain that the tags are redundant ( i.e. the tagged structures cannot repeat, and are never optional ).
Glad it's working. |
|
| 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
|
|
|
|
