| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MRM TDS Message Definition problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| satya2481 |
 Posted: Fri Dec 14, 2007 2:15 am Post subject: MRM TDS Message Definition problem |
 |
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
Hi All,
I always used to struggle while defining a message in MRM - TDS domain. My first question is do any body having any links or documents which will explain about TDS message sets clearly with more examples, except the documents which are available in IBM site under the WMB documents.
Now my real issue is I am trynig to define a message in MRM TDS domain and not able to do it correctly. Can any one help me on this issue...
| Code: |
Message structure is like this
Header - Level 1, Occurence 1-N
Field1 - Fixed length
Field2 - Fixed length
JOBRecord - Level 2, Occurence 1-N
Field1 - Fixed length
Field2 - Fixed length
PartRecord - Level 3, Occurence 0-N
Field1 - Fixed length
Field2 - Fixed length
SundryRecord - Level 3, Occurence 0-N
Field1 - Fixed length
Field2 - Fixed length
DOFRecord - Level 3, Occurence 0-N
Field1 - Fixed length
Field2 - Fixed length
Travel - Level 1, Occurence 1-1
Field1 - Fixed length
Field2 - Fixed length |
Sample message is like
101Field1Field2
103Field1Field2
104Field1Field2
105Field1Field2
106Field1Field2
102Field1Field2
How to define this kind of message correclty, I had tried so many combinations but ended up with one or other issue....
Can any one help me on this.
Thanks in advance
SSM
[/code]
_________________
IBM Certified Solution Developer WebSphere Message Broker V6.0
IBM Certified System Administrator WebSphere MQ V6.0 |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Dec 14, 2007 2:37 am Post subject: Re: MRM TDS Message Definition problem |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| satya2481 wrote: |
I had tried so many combinations but ended up with one or other issue....
|
What have you tried? What were the issues?
There's no point us suggesting stuff which has already failed to meet your needs. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| satya2481 |
| Posted: Fri Dec 14, 2007 3:08 am Post subject: |
|
|
Disciple
Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru
|
There is a small correction in my message structure....
| Code: |
Travel - Level 2, Occurence 1-1
Field1 - Fixed length
Field2 - Fixed length |
I tried to define the message like
| Code: |
Header - complex element;Occurence 1-N;DES=Variable length elements delimited; <CR><LF> delimiter; tag =101
Field1 - element;Fixed length
Field2 - element;Fixed length
JOBRecord - complex element;DES = tagged delimited; delimiter = <CR><LF>
JOB - complex element;Occurence 0-N;tag=103;DES=fixed length
Field1 - element;Fixed length
Field2 - element;Fixed length
PartRecord - complex element;Occurence 0-N;tag=104;DES=fixed length
Field1 - element;Fixed length
Field2 - element;Fixed length
SundryRecord - complex element;Occurence 0-N;tag=105;DES=fixed length
Field1 - element;Fixed length
Field2 - element;Fixed length
DOFRecord - complex element;Occurence 0-N;tag=106;DES=fixed length
Field1 - element;Fixed length
Field2 - element;Fixed length
Travel - complex element;Occurence 1-1;tag=102;DES=fixed length
Field1 - element;Fixed length
Field2 - element;Fixed length |
where DES = Data element separation
The parser not able to parse the mesage correclty, i am getting an error indicating buffer length not fully utilised...
_________________
IBM Certified Solution Developer WebSphere Message Broker V6.0
IBM Certified System Administrator WebSphere MQ V6.0 |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Fri Dec 14, 2007 4:39 am Post subject: Re: MRM TDS Message Definition problem |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi satya2481,
| satya2481 wrote: |
101Field1Field2
103Field1Field2
104Field1Field2
105Field1Field2
106Field1Field2
102Field1Field2 |
Try this
For Header:
* Group Indicator = 101
* Group Terminator = <CR><LF>
* Data Element Separation = Fixed Length (define length of fields within)
Similarly for all....using their specific Group indicators...
For the section JOBRecord you might have to set Composition = unordered set, if the child records can come in random...
Regards. |
|
| 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
|
|
|
|
