| Author |
Message
|
| tnguyen |
 Posted: Thu Sep 21, 2006 6:11 pm Post subject: EDIFACT parser error after mqsi 2.1 to wmb 6.0.0.2 upgrade |
 |
|
Newbie
Joined: 12 Apr 2005
Posts: 3
|
Hi all,
I have just upgraded a v2.1 broker to v6, and successfully redeploy a message flow. But the flow errors out when it got to use an edifact message set which was also migrated.
I can't find any references to bip5604E. Has anyone seen this before?
thanks,
Trung
ParserException BIP5604E: Missing markup following a complex child or group
No markup was found following the complex child or group 'UNA_type'. The parent of this child or group has a Data Element Separation of 'All Elements Delimited' or 'Variable Length Elements Delimited'. All complex children within a type or group with a Data Element Separation of 'All Elements Delimited' or 'Variable Length Elements Delimited' must be followed by some markup. That is a 'Repeating Element Delimiter', a 'Delimiter', a 'Group Terminator' or some markup from a higher level in the message model. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Fri Sep 22, 2006 4:05 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Have you applied the latest runtime fixpack? |
|
| Back to top |
|
|
| tnguyen |
| Posted: Sun Sep 24, 2006 5:45 am Post subject: |
|
|
Newbie
Joined: 12 Apr 2005
Posts: 3
|
Hi,
yes, I have applied fixpack 2.
Trung |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Sep 25, 2006 12:44 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Sounds like a defect - please raise a PMR with IBM. In the meantime feel free to post relevant details of the message model and bitstream ( if you can cut it down small enough ) in case we can help via this forum. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Sep 26, 2006 12:27 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Did you raise a PMR? If so, please add a note indicating that this is a known defect, and there is a fix available. Please reference this topic so that the IBM service folks can contact me. You can expect this to be fixed in the next fixpack. |
|
| Back to top |
|
|
| asardinas |
| Posted: Tue Oct 31, 2006 8:55 am Post subject: Missing markup following a complex child or group |
|
|
Newbie
Joined: 04 Feb 2005
Posts: 4
|
| You said that there was a fix for this issue. I am also getting the same error and would like information on the patch. Also is there a workaround for this |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 31, 2006 9:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You probably have to open a PMR to get information or the patch.
They should be able to give you a workaround if there is a known one, too.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Oct 31, 2006 2:42 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
contact admin, tnguyen,
Please proceed with raising PMRs so that you get any fixes which are available.
In the meantime, this workaround may help:
This exact problem has been observed when the message definition contains two structures with the following TDS settings:
- The outer structure has Data Element Separation of All Elements Delimited
- The inner structure has Data Element Separation of Tagged Delimited or Tagged Fixed Length or Tagged Encoded Length.
If your message definition has a pair of structures like this, change the Data Element Separation of the outer structure to 'Tagged Delimited' and set the Tag Length property to 0. Redeploy the message set and retest. |
|
| Back to top |
|
|
|
|
