| Author |
Message
|
| dipankar |
 Posted: Wed Mar 29, 2006 2:55 am Post subject: TDS Message Set problem with MB 6 |
 |
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
Environment: MB 6.0, no Fix pack, WINDOWS 2000
Input Message Format:
EDI_DC40 300000000000019905646C 3014 ZPOST01
Z2EDPSHD000 300000000000019905600000100000002HRPAY0000000653
Z2EDPSPT000 300000000000019905600000200000002DE011HRP1
Z2EDPSPT000 300000000000019905600000300000002DE011HRP1
Z2EDPSPT000 300000000000019905600000400000002DE011HRP1
Z2EDPSPT000 300000000000019905600000500000002DE011HRP1
Z2EDPSPT000 300000000000019905600000600000002DE011HRP1
EDI_DC40 300000000000019905746C 3014 ZPOST01
Z2EDPSHD000 300000000000019905600000100000002HRPAY0000000653
Z2EDPSPT000 300000000000019905600000200000002DE011HRP1
Z2EDPSPT000 300000000000019905600000300000002DE011HRP1
-------
-------
Format:
| Code: |
CONTENT*
HDR1
HDR2
DATA * |
Here I had used Tag Delimiter for MQSI 2.1, CSD 08, WIN 2K. That is working fine.
Now I am using MB 6. The same way I have created message set. But it upsets me. After that I have migrated the message set 2.1 to 6. But the result remains same.
When I give the input like
it is working fine.
When I give input like
| Code: |
HDR1
HDR2
DATA*
HDR1
HDR2
DATA* |
it is creating exception that MRM parsing error; Message bit stream larger than expected
The second repetition is not working.
I have tried with several way. But all efforts are in vain.
Is it fix pack problem? Should I install fix pack 1. But WIN 2k is not supported by MB6. What should I do?
_________________
Regards |
|
| Back to top |
|
 |
| juddg |
| Posted: Wed Mar 29, 2006 4:34 am Post subject: More information please |
|
|
Apprentice
Joined: 22 Nov 2004
Posts: 33
|
Hi dipankar,
Please could you supply the following information about your message set:
The maxOccurs and TDS properties of the CONTENT, HDR1, HDR2 and DATA elements.
The type composition and TDS properties of the Types of CONTENT, HDR1, HDR2 and DATA elements.
Regards,
juddg. |
|
| Back to top |
|
|
| dipankar |
| Posted: Wed Mar 29, 2006 4:43 am Post subject: |
|
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
Message Set Structure:
| Code: |
CONTENT min Occurs 1 Max Occurs -1
Type Composition: Ordered Set
Data Element Separation: Tagged Delimited
Delimiter: <CR><LF>
Length of Tag: 8
HDR1 min occurs 1 Max Occurs 1
Tag: EDI_CC40
HDR1 min occurs 1 Max Occurs 1
Tag: Z2EDPSHD
DATA min occurs 1 Max Occurs -1
Tag: Z2EDPSPT
Repeating Element delimiter: <CR><LF> |
_________________
Regards |
|
| Back to top |
|
|
| dsriksha |
| Posted: Wed Mar 29, 2006 7:25 am Post subject: |
|
|
Voyager
Joined: 27 Feb 2005
Posts: 95
|
| dipankar wrote: |
Message Set Structure:
| Code: |
CONTENT min Occurs 1 Max Occurs -1
Type Composition: Ordered Set
Data Element Separation: Tagged Delimited
Delimiter: <CR><LF>
Length of Tag: 8
[color=blue] HDR1 min occurs 1 Max Occurs 1
Tag: EDI_CC40
HDR1 min occurs 1 Max Occurs 1
Tag: Z2EDPSHD[/color]
DATA min occurs 1 Max Occurs -1
Tag: Z2EDPSPT
Repeating Element delimiter: <CR><LF> |
|
you need to set also other field max to -1 . |
|
| Back to top |
|
|
| juddg |
| Posted: Wed Mar 29, 2006 9:01 am Post subject: Fiurther questions |
|
|
Apprentice
Joined: 22 Nov 2004
Posts: 33
|
Hi,
In the V6.0 message set editor I have created a message whose complex type is defined as described for content. This type contains 3 children HDR1, HDR2 and DATA with the tags specifed (I take it that the tag name of EDI_CC40 was a typo and is actually EDI_DC40) and of type string for test purposes. I can then successfully parse the message you supplied in V6.0.
If you create a message set from scratch do you still get the error? Has the message set that you using been imported into the V6.0 message set editor and then deployed to the V6.0 broker or are you using message sets that had already been deployed to the broker before upgrading to V6.0?
Regards,
juddg. |
|
| Back to top |
|
|
| dipankar |
| Posted: Wed Mar 29, 2006 7:36 pm Post subject: |
|
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
dsriksha wrote:
| Code: |
dipankar wrote:
Message Set Structure:
Code:
CONTENT min Occurs 1 Max Occurs -1
Type Composition: Ordered Set
Data Element Separation: Tagged Delimited
Delimiter: <CR><LF>
Length of Tag: 8
[color=blue] HDR1 min occurs 1 Max Occurs 1
Tag: EDI_CC40
HDR1 min occurs 1 Max Occurs 1
Tag: Z2EDPSHD[/color]
DATA min occurs 1 Max Occurs -1
Tag: Z2EDPSPT
Repeating Element delimiter: <CR><LF>
you need to set also other field max to -1 . |
What is that other field? Please give me details. I have also migrated the message set of 2.1 to 6 that is also not working. I don't think there is any problem in the message set as message set in 2.1 is working fine.
juddg wrote:
| Code: |
| In the V6.0 message set editor I have created a message whose complex type is defined as described for content. This type contains 3 children HDR1, HDR2 and DATA with the tags specifed (I take it that the tag name of EDI_CC40 was a typo and is actually EDI_DC40) and of type string for test purposes. I can then successfully parse the message you supplied in V6.0. |
EDI_CC40 is a typo mistake. Is the second repitition which I mentioned above working? What wrong is with my message set?
| Code: |
| If you create a message set from scratch do you still get the error? Has the message set that you using been imported into the V6.0 message set editor and then deployed to the V6.0 broker or are you using message sets that had already been deployed to the broker before upgrading to V6.0? |
MB 6 has been installed in another system. So no need to upgrade broker. Everything is new in MB6. I have created message set, not imported in MB6.
_________________
Regards |
|
| Back to top |
|
|
| juddg |
| Posted: Thu Mar 30, 2006 7:14 am Post subject: |
|
|
Apprentice
Joined: 22 Nov 2004
Posts: 33
|
Hi dipankar,
The structure of your message is :
| Code: |
Message
Type Composition: Ordered Set
Data Element Separation: All Elements Delimited
Delimiter: <CR><LF>
CONTENT min Occurs 1 Max Occurs -1
Type Composition: Ordered Set
Data Element Separation: Tagged Delimited
Delimiter: <CR><LF>
Length of Tag: 8
[color=blue] HDR1 min occurs 1 Max Occurs 1
Tag: EDI_CC40
HDR1 min occurs 1 Max Occurs 1
Tag: Z2EDPSHD[/color]
DATA min occurs 1 Max Occurs -1
Tag: Z2EDPSPT
Repeating Element delimiter: <CR><LF>
|
This message structure should validly parse your data but there is a problem with the parser in V6.0. Therefore please can you raise a PMR referencing this forum entry.
As a workaround you can change the type of the message as follows:
| Code: |
Message
Type Composition: Ordered Set
Data Element Separation: Tagged Delimited
Delimiter: <CR><LF>
Tag Data Separator: # (Note this isn't actually used)
|
Regards,
juddg. |
|
| Back to top |
|
|
| dipankar |
| Posted: Thu Mar 30, 2006 10:43 pm Post subject: |
|
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
juddg,
I do not know how to raise PMR. Could you help me?
_________________
Regards |
|
| Back to top |
|
|
| shanson |
| Posted: Fri Mar 31, 2006 12:33 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| By 'raising a PMR' we simply mean contact IBM service, using the usual channels. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Mar 31, 2006 3:53 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Why are you not using the IDOC parser and IDOC type?
You need to download the C headers from WE60. Run them through the perl script (sets the filler to get to a total of 1000 char in sdata) and import it as IDOC. You should probably be at FP 1 on the toolkit.
Worked fine for me. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| dipankar |
| Posted: Sun Apr 02, 2006 9:59 pm Post subject: |
|
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
Hi fjb_saper,
| Quote: |
| Why are you not using the IDOC parser and IDOC type? |
I never used it. I will try to use IDOC parser in future. So as per your view, the only option is to use IDOC parser. Is it correct?
I had used MRM parser with TDS format in MQSI 2.1 as mentioned before. It is still working fine. I have migrated the message set 2.1 to 6. But it creates exception. What will you say here?
_________________
Regards |
|
| Back to top |
|
|
| shanson |
| Posted: Tue Apr 04, 2006 12:37 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| Sorry, I'm getting lost here. Are these messages from SAP? If they are, and the data is IDOCs, then you can use the IDOC parser (which calls MRM CWF to parse the user data). If they are not from SAP, stick with MRM TDS. |
|
| Back to top |
|
|
| dipankar |
| Posted: Tue Apr 04, 2006 1:18 am Post subject: |
|
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
shanson
| Code: |
| Are these messages from SAP? |
I don't know. I don't have any concern with SAP. Client sent the input message only as mentioned before.
fjb_saper wrote:
| Quote: |
| Why are you not using the IDOC parser and IDOC type? |
That's why I was thinking on IDOC parser. However I believe I should use MRM TDS. But there is an issue with parser in MB6. You will not be able to parse the above message in MB6. I have tried many times with many combinations. But everytimes it made me upset. However I had designed the message set in MQSI 2.1 with CSD08 which successfully parsed the above message. No issue I have ever found in MQSI 2.1.
Here is my observation:
CONTENT is a compound element. (multiple occurrence)
It child element is
HDR1
HDR2
DATA (multiple occurrence)
As DATA has repeating element delimiter <CR><LF> and CONTENT element has repeating element delimiter <CR><LF>, MB6 mrm parser is looking for an extra <CR><LF> after the end of DATA section. Please look here
| Code: |
EDI_DC40 300000000000019905646C 3014 ZPOST01
Z2EDPSHD000 300000000000019905600000100000002HRPAY0000000653
Z2EDPSPT000 300000000000019905600000200000002DE011HRP1
Z2EDPSPT000 300000000000019905600000300000002DE011HRP1
Z2EDPSPT000 300000000000019905600000400000002DE011HRP1
Z2EDPSPT000 300000000000019905600000500000002DE011HRP1
Z2EDPSPT000 300000000000019905600000600000002DE011HRP1
EDI_DC40 300000000000019905746C 3014 ZPOST01
Z2EDPSHD000 300000000000019905600000100000002HRPAY0000000653
Z2EDPSPT000 300000000000019905600000200000002DE011HRP1
Z2EDPSPT000 300000000000019905600000300000002DE011HRP1 |
Look carefully. I have added an extra <CR><LF> at the end of DATA section. It is being successfully parsed. Did you get my point?
_________________
Regards |
|
| Back to top |
|
|
| shanson |
| Posted: Tue Apr 04, 2006 1:50 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
We understand your point, that's why we have already told you to contact IBM service to get a resolution to your problem. We have found the cause, and we are developing a fix. Or you can use the workaround supplied by juddg above.
Note that the same problem has also been found by another customer, the PMR raised is 01293,B999,C796. Please quote this PMR number when you or your client contact IBM service. |
|
| Back to top |
|
|
|
|
