| Author |
Message
|
| cnurao_008 |
 Posted: Thu Jul 02, 2009 10:05 pm Post subject: carzy Broker |
 |
|
Apprentice
Joined: 25 Nov 2008
Posts: 30
|
Hello All,
I am new to this broker 6.1.I have the following problem.
I have one MRM message set. I when i tested my flow Mqinput - trace - Mqout node.
It's throws an TDS error. When i tesed with debug mode. it is able to process it. I do n't understad this behaviour of broker. Hoe come it 's posible.
Can any one suggest me. How i can do this with out debugger. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu Jul 02, 2009 10:46 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
As you have put a Trace node in the main path of the flow, I suggest you add another one to the 'Catch' terminal of the Input Node and capture the ExceptionList and post it here.
This will help but as you are new to Broker then starting with a TDS Message is just asking for trouble unless you have received some decent training (you have haven't you?)
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| namakkal |
| Posted: Thu Jul 02, 2009 10:48 pm Post subject: Re: carzy Broker |
|
|
Novice
Joined: 06 Feb 2009
Posts: 19
|
| cnurao_008 wrote: |
Hello All,
I am new to this broker 6.1.I have the following problem.
I have one MRM message set. I when i tested my flow Mqinput - trace - Mqout node.
It's throws an TDS error. When i tesed with debug mode. it is able to process it. I do n't understad this behaviour of broker. Hoe come it 's posible.
Can any one suggest me. How i can do this with out debugger. |
It might be the problem with Message set. can you tell me what error your getting? are you trying to write in file |
|
| Back to top |
|
|
| cnurao_008 |
| Posted: Thu Jul 02, 2009 11:33 pm Post subject: |
|
|
Apprentice
Joined: 25 Nov 2008
Posts: 30
|
Here is the error.
<ErrorMsg>
<TimeOfError>2009-07-03 12:56:12.525989</TimeOfError>
<MsgId>414d5120424b525f514d475220202020ab6b234a20663d19</MsgId>
<SourceQueue>IN</SourceQueue>
<PutApplName>SA RAO\SOFT\IH03\rfhutil.exe</PutApplName>
<PutDate>2009-07-03</PutDate>
<PutTime>07:26:11.610</PutTime>
<ExceptionMsg>
<File>F:\build\S610_P\src\DataFlowEngine\ImbTraceNode.cpp</File>
<Line>341</Line>
<Function>ImbTraceNode::evaluate</Function>
<Type>ComIbmTraceNode</Type>
<Name>ALEIDOC_MSGLFW#FCMComposite_1_2</Name>
<Label>ALEIDOC_MSGLFW.Trace</Label>
<Catalog>BIPv610</Catalog>
<Severity>3</Severity>
<Number>2230</Number>
<Text>Caught exception and rethrowing</Text>
<ParserException>
<File>F:\build\S610_P\src\MTI\MTIforBroker\MtiImbParser2\MtiImbParser.cpp</File>
<Line>730</Line>
<Function>MtiImbParser::parseRightSibling</Function>
<Type>ComIbmMQInputNode</Type>
<Name>ALEIDOC_MSGLFW#FCMComposite_1_1</Name>
<Label>ALEIDOC_MSGLFW.MQInput</Label>
<Catalog>BIPv610</Catalog>
<Severity>3</Severity>
<Number>5285</Number>
<Text>ImbRecoverableException caught from worker->parseNext.</Text>
<Insert>
<Type>5</Type>
<Text>ALEIDOC.MSGSET.PROJ</Text>
</Insert>
<Insert>
<Type>2</Type>
<Text>1</Text>
</Insert>
<Insert>
<Type>5</Type>
<Text>Text_IDoc</Text>
</Insert>
<Insert>
<Type>5</Type>
<Text>/ALE_IDoc/DD/sdatatag</Text>
</Insert>
<ParserException>
<File>F:\build\S610_P\src\cpi\pwf\nxd\nxdworker.cpp</File>
<Line>462</Line>
<Function>NXDWorker::parseNext</Function>
<Type></Type>
<Name></Name>
<Label></Label>
<Catalog>BIPv610</Catalog>
<Severity>3</Severity>
<Number>5421</Number>
<Text>TDS General Error</Text>
<Insert>
<Type>5</Type>
<Text>ALE_IDoc</Text>
</Insert>
<Insert>
<Type>5</Type>
<Text>/ALE_IDoc/[SEQUENCE](1 of unbounded)/DD(31 of unbounded)/sdatatag</Text>
</Insert>
<Insert>
<Type>2</Type>
<Text>32477</Text>
</Insert>
<ParserException>
<File>F:\build\S610_P\src\MTI\MTIforBroker\MtiImbParser2\MtiImbFIHandler.cpp</File>
<Line>2913</Line>
<Function>MtiImbFIHandler::startEmbeddedMessage(int&, int&)</Function>
<Type></Type>
<Name></Name>
<Label></Label>
<Catalog>BIPv610</Catalog>
<Severity>3</Severity>
<Number>5153</Number>
<Text>Message type got from message identity field was not found in the dictionary</Text>
<Insert>
<Type>5</Type>
<Text>ALEIDOC.MSGSET.PROJ</Text>
</Insert>
<Insert>
<Type>5</Type>
<Text> E2EDL43000 </Text>
</Insert>
</ParserException>
</ParserException>
</ParserException>
</ExceptionMsg>
</ErrorMsg> |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jul 02, 2009 11:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I suspect the wrong padding length at the end of the segment's sdata section.
The EDI_DD40 is of 1063 length and it's sdata section is 1000 char/bytes long
So if you had the segment defined as COBOL cpy book (easier than c struct because it will support default values from SAP), you have to remember to add the pad / filler at the end of the segment to normalize it's size...
By the way for SAP I go for the IDOC parser. Don't know if it does MRM TDS behind the scenes... would make sense though as each segment is tagged with it's name...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jul 03, 2009 12:44 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| It's throws an TDS error. When i tesed with debug mode. it is able to process it. I do n't understad this behaviour of broker. Hoe come it 's posible. |
This is a known problem with the debugger. Please disconnect the debugger and take a user trace.
- you will get to see a nicely formatted version of the error, with a lot more information than the exception list shows you
- you will get an execution trace from the TDS parser as part of the user trace output.
There are several posts on this forum explaining how to take a user trace. |
|
| Back to top |
|
|
|
|
