| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Dictionary not found for message set DS0FSJ407E001 |
« View previous topic :: View next topic » |
| Author |
Message
|
| mehedi |
 Posted: Tue Mar 18, 2003 8:11 am Post subject: Dictionary not found for message set DS0FSJ407E001 |
 |
|
Centurion
Joined: 11 Nov 2001
Posts: 102
Location: PSTech
|
This is the error message from the log.
"Dictionary not found for message set DS0FSJ407E001 - BIP5304E"
This is the code in the Compute Nodes in the flow.
SET OutputRoot.Properties.MessageSet = 'DS0FSJ407E001';
SET OutputRoot.Properties.MessageType = 'PROMPT';
SET OutputRoot.Properties.MessageDomain = 'MRM';
SET OutputRoot.Properties.MessageFormat = 'CWF';
SET OutputRoot.Properties.MessageSet = 'DS0FSJ407E001';
SET OutputRoot.Properties.MessageType = 'PROMPT_OUT';
SET OutputRoot.Properties.MessageDomain = 'MRM';
SET OutputRoot.Properties.MessageFormat = 'CWF';
When this message set is reffered to in another flow in an MQinput Node it works.
What could be wrong ?
_________________
Thanks
Mehedi Hashir
mhashir@hotmail.com |
|
| Back to top |
|
 |
| mehedi |
| Posted: Tue Mar 18, 2003 12:44 pm Post subject: Parsing in 2.1 vs 2.0.2 |
|
|
Centurion
Joined: 11 Nov 2001
Posts: 102
Location: PSTech
|
Two part fix to the problem
- The message set we were using in the flow was an exact copy of another message set. When the orginal message set was used this problem went away. Don't ask me how.
- Then we came up against the next
The first compute node in the message flow stores field values in
(a) MessageLayout1 of message set X of type MRM
The second compute node in the message flow does a BITSTREAM(inputBody) and stores value returned and some new additional field values in
(b) MessageLayout2 of message set X of type MRM
The Bitstream(inputbody) function was returning a null value.
This was not the case when the flow was executing in MQSI 2.0.2.
This was resolved when we added a RCD and explicitly had the message parsed by (a) MessageLayout1 of message set X of type MRM before it was passed on to the second compute node.
I'm guessing this has something to do with how the parser works in 2.1 as opposed to how it worked in 2.0.2 - (lazy parse etc)
_________________
Thanks
Mehedi Hashir
mhashir@hotmail.com |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 18, 2003 1:15 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Quote: |
| - The message set we were using in the flow was an exact copy of another message set. When the orginal message set was used this problem went away. Don't ask me how. |
Each message set, regardless of it's contents, has it's own unique identifier. That is, if you copy a message set, it's got a new ID number.
If you changed your message flow to use the new message set, but didn't deply the new message set to the broker, you would see the error you reported. |
|
| Back to top |
|
|
| mehedi |
| Posted: Wed Mar 19, 2003 8:16 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2001
Posts: 102
Location: PSTech
|
Jeff,
I went through the whole cycle and made sure
The message set deployed was the same as referenced in the flow.
Somehow it still never works with the copy. I moving onto other stuff i thought it might be useful for people to know.
_________________
Thanks
Mehedi Hashir
mhashir@hotmail.com |
|
| 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
|
|
|
|
