| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TDS Message Set |
« View previous topic :: View next topic » |
| Author |
Message
|
| Rockon |
 Posted: Tue Nov 23, 2004 2:27 pm Post subject: TDS Message Set |
 |
|
Apprentice
Joined: 24 May 2004
Posts: 43
|
Hello All,
I have an issue w.r.t transformation of XML to TDS.The exception I have looks like this
| Quote: |
<ExceptionList>
- <RecoverableException>
<File>/build/S210_P/src/DataFlowEngine/ImbMqOutputNode.cpp</File>
<Line>715</Line>
<Function>ImbMqOutputNode::evaluate</Function>
<Type>ComIbmMQOutputNode</Type>
<Name>9a178161-0001-0000-0080-f69a28ff0a2e</Name>
<Label>INB100_UXINB500_INB.TEST_IN.INB.TEST_OUT</Label>
<Text>Caught exception and rethrowing</Text>
<Catalog>WMQIv210</Catalog>
<Severity>3</Severity>
<Number>2230</Number>
- <ParserException>
<File>/build/S210_P/src/MTI/MTIforBroker/MtiImbParser2/MtiImbRMErrorMap.cpp</File>
<Line>139</Line>
<Function>MtiImbRMErrorMap::checkRC</Function>
<Type />
<Name />
<Label />
<Text>RM Descriptor Not Found.</Text>
<Catalog>WMQIv210</Catalog>
<Severity>3</Severity>
<Number>5313</Number>
- <Insert>
<Type>2</Type>
<Text>32</Text>
</Insert>
- <Insert>
<Type>5</Type>
<Text>rmLoadWorker</Text>
</Insert>
- <Insert>
<Type>5</Type>
<Text>DQF1OCG0H4001</Text>
</Insert>
- <Insert>
<Type>5</Type>
<Text>TDS1</Text>
</Insert>
</ParserException>
</RecoverableException>
</ExceptionList>
|
Any help with this regard will be appreciated.
Thankyou,
Cheers |
|
| Back to top |
|
 |
| JT |
| Posted: Tue Nov 23, 2004 2:38 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
Explanation:
This means that either the message format had not been specified properly, a WFD resource has not been deployed, there is no Wire
Format Descriptor ’&4’ associated with message set ’&3’, the installation is not valid (corrupted or incomplete) or that an unknown bitstream worker has been requested at resource registration time or at run time. |
Check the wire format value that was assigned to the message set identified by DQF1OCG0H4001.
Is it truely TDS1? |
|
| Back to top |
|
|
| kirani |
| Posted: Tue Nov 23, 2004 11:26 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
| JT wrote: |
Is it truely TDS1? |
In V5, by default, the wire formats are named TDS1, XML1, CWF1, etc.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 24, 2004 4:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| kirani wrote: |
In V5, by default, the wire formats are named TDS1, XML1, CWF1, etc. |
| Rockon wrote: |
| <Catalog>WMQIv210</Catalog> |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Nov 30, 2004 1:26 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
I would double-check that
You have deployed the correct version of the message set dictionary The Message Set Identifier (DQF1OCG0H4001) is correctly set in the RFH2 header, the MQInput node properties or via your ESQL. The name 'TDS1' really is the same as the Wire Format Identifier in the Message Set
Note that if you are using 2.1, the default Wire Format Identifier for TDS is 'TDS' (not 'TDS1'). |
|
| Back to top |
|
|
| Rockon |
| Posted: Tue Nov 30, 2004 1:02 pm Post subject: |
|
|
Apprentice
Joined: 24 May 2004
Posts: 43
|
Yup...
TDS did the trick.....I am using 2.1
Thankyou all,
Cheers |
|
| 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
|
|
|
|
