| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TDS message not read if 2 delimeters are together & no v |
« View previous topic :: View next topic » |
| Author |
Message
|
| JoseR |
 Posted: Mon Jun 26, 2006 11:15 am Post subject: TDS message not read if 2 delimeters are together & no v |
 |
|
Novice
Joined: 23 Feb 2006
Posts: 24
|
I have the following message:
| Code: |
| MSH|^~\&|MSS_MSS|MCR|LAB3|MCR|20060613100100||ORM|.... |
Whe my message set parses the message, this is what I get:
| Code: |
<?xml version="1.0"?>
<MRM>
<ORM_ xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<MSH>
<MSH.2>^~\&</MSH.2>
<MSH.3>
<HD.1>MSS_MSS</HD.1>
</MSH.3>
<MSH.4>
<HD.1>MCR</HD.1>
</MSH.4>
<MSH.5>
<HD.1>LAB3</HD.1>
</MSH.5>
<MSH.6>
<HD.1>MCR</HD.1>
</MSH.6>
<MSH.7>20060613100100</MSH.7>
<MSH.8>ORM</MSH.8> |
the problem is that MSH.8 according to my message should be null or empty.
_________________
Jose R
WWJD
< ))><< |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Jun 27, 2006 1:51 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Hi JoseR,
I can help with this, but I'll need more information:
1. What version and CSD level are you using?
2. Did you construct the message set yourself, or are you using the HL7 solution hub from the Dublin lab?
3. The XML which you posted is the XML output message, not the results of the parse. Please put a trace node immediately after the parsing of the message ( with pattern ${Root} ) and post the relevant section of the output here.
4. Do the same with a trace node immediately before the MQOutput node. |
|
| Back to top |
|
|
| JoseR |
| Posted: Tue Jun 27, 2006 7:06 am Post subject: |
|
|
Novice
Joined: 23 Feb 2006
Posts: 24
|
Thanks for the reply,
I've seem to resolved this issue at least for now!
To answes some of your questions:
| Quote: |
| 1. What version and CSD level are you using? |
Version: 6.0.0.1
Build id: 20060106_1130
I believe the CSDF is 4
| Quote: |
| 2. Did you construct the message set yourself, or are you using the HL7 solution hub from the Dublin lab? |
I constructed the message myself thought we are negociating with IBM for the HL7 solution hub.
| Quote: |
| 3. The XML which you posted is the XML output message, not the results of the parse. Please put a trace node immediately after the parsing of the message ( with pattern ${Root} ) and post the relevant section of the output here. |
| Code: |
(0x0100001B):MRM = (
(0x01000013):MSH = (
(0x03000013):MSH.2 = '^~\&'
(0x01000013):MSH.3 = (
(0x03000013):HD.1 = 'MSS_MSS'
)
(0x01000013):MSH.4 = (
(0x03000013):HD.1 = 'MCR'
)
(0x01000013):MSH.5 = (
(0x03000013):HD.1 = 'LAB3'
)
(0x01000013):MSH.6 = (
(0x03000013):HD.1 = 'MCR'
)
(0x03000013):MSH.7 = '20060613100100'
(0x01000013):MSH.9 = (
(0x03000013):CM_MSG.1 = 'ORM'
)
(0x03000013):MSH.10 = '2006061310010003151097'
(0x01000013):MSH.11 = (
(0x03000013):PT.1 = 'P'
)
(0x03000013):MSH.12 = '2.3'
) |
| Quote: |
| 4. Do the same with a trace node immediately before the MQOutput node. |
The output is the same becasue it am copying the input root to output root.
Here it is what I thought it happen and here it is what I did:
1.) What I thought it happen is that my message Set was eatting an 2 delimetters "||" at once but I do not know why
2.) What I did to resolve the issue was to remove the delimeter definition for my message Set under the Physical Properties of my HL7 format settings.
Doing this, I end up defining the delimeters for every HL7 segment under my definition schema e.g. MSH, PID,PV1,PV2,ORC,OBX..etc (my message being a OBR message) treating every HL7 segment as a Group.
Complicated, but once set it works for the most part.
There are still one or two fields where the MRM parser does not line up with the original message and I am still working with it 
_________________
Jose R
WWJD
<))><< |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jun 27, 2006 7:25 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I believe the CSDF is 4 |
There's only one Fix Pack for v6 so far. You're on FP1.
| Quote: |
| we are negociating with IBM for the HL7 solution hub |
Good idea.
| Quote: |
| 1.) What I thought it happen is that my message Set was eatting an 2 delimetters "||" at once but I do not know why |
When the parser sees two consecutive delimiters, it does not write anything to the message tree. ( you might prefer it to write an element with no value, but that can cause problems with dates and other non-string data types ). This is why you see MSH.9 immediately after MSH.7 in your trace output.
| Quote: |
| There are still one or two fields where the MRM parser does not line up with the original message and I am still working with it |
A little bit of advice: don't try to debug your message set by looking at the XML output. Always use a trace node to inspect the message tree which the parser has built. |
|
| 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
|
|
|
|
