| Author |
Message
|
| Heurton |
 Posted: Tue Jan 17, 2006 3:22 am Post subject: Idoc problem after WMQI V2.1 to WMB V6 migration |
 |
|
Novice
Joined: 19 Nov 2003
Posts: 16
|
Hi all,
I migrated a WMQI V2.1 flow to WMB V6. This flow has XML message in input and an Idoc output message.
With the same data in input, in WMQI V2 I got the full idoc in the output queue, but with WMB V6, I got only the first segment (EDI DC40) in the output queue. I have a trace just before the MQoutput node, and the Idoc is OK!
For your information, I work with Websphere MQ V6.
Has somebody an idea?
Thanks in advance for your help |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Tue Jan 17, 2006 8:19 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi Heurton,
The most probable reason could be that the IDoc has not been migrated properly, check if all the schema's are available and the entire message is available in the message set.
Regards. |
|
| Back to top |
|
|
| Heurton |
| Posted: Thu Jan 19, 2006 12:39 am Post subject: |
|
|
Novice
Joined: 19 Nov 2003
Posts: 16
|
Hi elvis_gn
I've checked the migration log,and the messages in the message set and they are OK.
I've tested with a flow which has an IDOC as input and in WMB V6 the first fields before sdatatag contains the datas!
below traces of the same IDOC processed with WMQI V2 and WMB V6 after migrating the flow and message set
WMQI V2.1:
(0x1000000)DD = (
(0x3000000)segnam = 'Z2EDK01PSA000 '
(0x3000000)mandt2 = ' '
(0x3000000)docnum2 = ' '
(0x3000000)segnum = ' '
(0x3000000)psgnum = ' '
(0x3000000)hlevel = ' '
(0x1000000)sdatatag = (
(0x1000021)MRM = (
(0x300000B)belnr = '4200003771 '
(0x300000B)vbeln = '0000006313'
(0x300000B)date = '20051205T17:04:00'
(0x300000B)origin = 'ORIGINAL '
(0x300000B)ident = '0090 '
(0x300000B)ihrez = '81381GAC01 '
(0x300000B)pad863 = '
WMB V6:
(0x01000000)DD = (
(0x03000000):segnam = 'Z2EDK01PSA000 '
(0x03000000):mandt2 = '420'
(0x03000000):docnum2 = '0003771 '
(0x03000000):segnum = ' '
(0x03000000):psgnum = ' '
(0x03000000):hlevel = ' '
(0x01000000):sdatatag = (
(0x01000021):MRM =
I think these 2 problems have the same source, but I didn't find the solution!
Have you an idea?
Thanks for your response |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Thu Jan 19, 2006 8:29 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi Heurton,
have you got the problem fixed ?
I would have expected one of the schemas in the message set to be missing....i guess thats not the case.
You could check your message against XMLSpy or so, if the namespace is wrong, that would explain why the segment did not appear...
Also, we could have a look at the code snippet for this segment...
Regards. |
|
| Back to top |
|
|
| shanson |
| Posted: Fri Jan 20, 2006 4:01 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
We think this is a problem in WMB V6. It looks like spaces at the end of the message name are causing the message not to be recognised by the MRM. I can see from your trace below that there is a space at the end of the DD segnam data. If you can trim the DD segnam field so that this space is removed, you should find that the MRM finds the message. (Whether that causes SAP a problem down the line I don't know, but let's tackle that later).
This is a regression and we'll get the fix into the next V6 fixpack. |
|
| Back to top |
|
|
| Heurton |
| Posted: Wed Feb 01, 2006 6:12 am Post subject: |
|
|
Novice
Joined: 19 Nov 2003
Posts: 16
|
Hi all,
it was a problem in WMB V6. I received a fix and now, it works!
Thanks for your responses |
|
| Back to top |
|
|
| shanson |
| Posted: Wed Feb 01, 2006 8:24 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| We believe there is also an issue when writing SAP IDocs too, where the MRM is not being invoked to write the MRM CWF part of the data. A fix is being worked on and will be in the next Fix Pak. If you encounter this problem please raise a PMR. |
|
| Back to top |
|
|
| Ozmanyyy |
| Posted: Tue Feb 21, 2006 11:52 am Post subject: |
|
|
Newbie
Joined: 21 Feb 2006
Posts: 2
Location: North East
|
| Heurton wrote: |
Hi all,
it was a problem in WMB V6. I received a fix and now, it works!
Thanks for your responses |
I must be having the same problem. I get an error saying that there is no message that matches the type:
<<<<The CWF parser or writer has received an unknown message type identifier in the message properties.
The specified message set (''GSVN6QO002001'') does not contain a message type with this identifier. >>>> snipped
My trace has the following:
(0x01000000) D = (
(0x03000000):segnam = 'E2KNA1M005 '
I do have a message named E2KNA1M005 in my message definition, so I suspect the spaces are whats killing me.
So, when you say you recieved a fix, did you mean there is a fixpack somewhere for this ? ( I am using MB ver 6 also ). Or is there a way to trim the spaces ?
Thanks for any input...
Oz |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Feb 21, 2006 6:07 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
As well if you want to import an IDOC definition in V6 make sure no field is name "compl". The Message Definition import function does not like this field. I guess the fix will be in the next Fix Pack...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Feb 22, 2006 1:54 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
See the previous post
| Quote: |
| A fix is being worked on and will be in the next Fix Pak. If you encounter this problem please raise a PMR. |
If you can wait for the next FixPak, do so. Otherwise raise a PMR. |
|
| Back to top |
|
|
| shanson |
| Posted: Wed Feb 22, 2006 3:26 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| Quote: |
As well if you want to import an IDOC definition in V6 make sure no field is name "compl". The Message Definition import function does not like this field. I guess the fix will be in the next Fix Pack...
|
The problem with compl is that it is a C++ pre-processor keyword (see http://david.tribble.com/text/cdiffs.htm) and is rejected by the underlying C importer. There are no plans to fix this. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Feb 22, 2006 5:38 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| If you decide to raise a PMR, the APAR number of the fix you require is IC47696. |
|
| Back to top |
|
|
| Ozmanyyy |
| Posted: Wed Feb 22, 2006 6:31 am Post subject: |
|
|
Newbie
Joined: 21 Feb 2006
Posts: 2
Location: North East
|
| kimbert wrote: |
| If you decide to raise a PMR, the APAR number of the fix you require is IC47696. |
Thanks for the help guys, I will rais a pmr |
|
| Back to top |
|
|
| Ramphart |
| Posted: Thu May 18, 2006 5:35 am Post subject: |
|
|
Disciple
Joined: 21 Jul 2004
Posts: 150
Location: South Africa, JHB
|
| shanson wrote: |
| We believe there is also an issue when writing SAP IDocs too, where the MRM is not being invoked to write the MRM CWF part of the data. A fix is being worked on and will be in the next Fix Pak. If you encounter this problem please raise a PMR. |
Hi,
Can anyone tell me if this issue has been resolved? I'm trying to write out IDOCS using Broker 6 (fix 6.0.0.1) and the CWF portion of the IDOC is not being written as part of the output message.
Thx
_________________
Applications Architect |
|
| Back to top |
|
|
| shanson |
| Posted: Thu May 18, 2006 7:04 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| This problem is fixed in WMB V6 runtime fix pack 6.0.0.1. Please make sure you have the runtime fix pack applied as well as the toolkit fix pack, which came out a couple of months before. |
|
| Back to top |
|
|
|
|
