| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TDS message set definiftion help |
« View previous topic :: View next topic » |
| Author |
Message
|
| madi |
 Posted: Wed Aug 27, 2008 12:48 pm Post subject: TDS message set definiftion help |
 |
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
I have a message for mat like this
| Code: |
10~data1~data2~..........
20~data1~data2~data3.........
30~data1~data2.........
20~data1~data2~............
20~data1~data2~............
|
there can be many 10 records, each 10 can have many 20s, each 20 can have 0 or more 30s
now i defined the 10, 20 and 30 records separately as delimited with ~ and that is fine
i am not able to successfully put them together though making sure the hierarchy is maintained
if i define
| Quote: |
ComplexType "Message" -> Tagged Del with "~" as seperator
ComplexType "10 record" with tag 10
ComplexType "20 record" with tag 20
|
but then 20 has to go into 10 and not below it? does someone have a cleaner and easier way to do this?
--madi
_________________
IBM Certified Solutions Developer - WMB 6.0 |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Aug 27, 2008 2:42 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Hi madi,
You need to go back to basics here. The structure of the message tree is determined by the structure of the message definition. So...
- Write down the structure of the message tree that you want to get
- Create a new message
- Under the new message, create elements and complex types in exactly the structure that you created in the first step. The Outline view of the message ( when fully expanded ) should look exactly like the message tree that you want to work with.
- Set Data Element Separation, delimiters, group terminators etc on all elements and complex types.
You can probably modify your existing message definition to achieve the same result, provided that you remember the golden rule : message tree structure always matches the structure of the complex types and elements in the message definition. |
|
| Back to top |
|
|
| broker_new |
| Posted: Wed Aug 27, 2008 5:24 pm Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
All u need to do is...
Create a type called
data1_type and add all the local elements under it..
delimiter will be ~.
Create one more type called data2_type
delimiter would be ~.
Create other type called data3_type
delimiter would be ~
Create another type called data2_type_data3_type
and under that create a type called data2_type and reference it to data2_type and in the same way create a type called data3_type and reference it to data3_type.
delimiter would be <LF>
Create another type called data1_type_data2_type_data3_type
and under that create a type called data1_type and reference it to data1_type and in the same way create a type called data2_type_data3_type and reference it to data2_type_data3_type.
delimiter would be <LF>.......
I think this is more descriptive and confusing ....try importing some samples and try then proceed with this.... |
|
| Back to top |
|
|
| madi |
| Posted: Thu Aug 28, 2008 5:40 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
thanks guys
it seems i was missing the whole concept of "groups" 
once i knew something called a "group" existed, i followed Kimbert's instructions in another post and got it defined
--madi
_________________
IBM Certified Solutions Developer - WMB 6.0 |
|
| 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
|
|
|
|
