| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problems with XML to MM (Cobol) Conversion |
« View previous topic :: View next topic » |
| Author |
Message
|
| j1 |
 Posted: Fri Jul 18, 2003 10:47 am Post subject: Problems with XML to MM (Cobol) Conversion |
 |
|
Centurion
Joined: 23 Jun 2003
Posts: 139
|
Hi,
I am trying to convert an incoming XML message to an MRM Cobol message. I have imported the copybook into a message set, created the
message flow etc.. when i deploy and try to test it, the trace indicates that
there is a problem after all the fields have been parsed and before once the CWFWriter actually starts writing the fields to Output. The first field is an X(1) filler and the error is being thrown on the second field called A-TRS-ACCT whch is X(14) and is a 14 char substring of an incoming 27 char string. The error log is as follows. do i need to apply an additional patch... The problems seems to be with the message dictionary.
2003-07-18 14:11:33.355998 1820 ImbMqOutputNode::evaluate
2003-07-18 14:11:33.355998 1820 MtiImbParser::subSyncWithDictionary , moveToFirstChild, DU3MFDO08E001, A-TRS-ACCT
2003-07-18 14:11:34.388000 1820 UserTrace BIP2631I: Backed out message being propagated to failure terminal; node 'IssuerefundCheck.IssuerefundCheckInput'.
Node 'IssuerefundCheck.IssuerefundCheckInput' has received a message which has previously been backed out because of a processing error in the message flow. The MQMD 'backoutCount' of the message exceeds (or equals) the 'backoutThreshold' defined for the MQSeries input queue. The message broker is propagating the message to the failure terminal of the node.
Examine the other messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
2003-07-18 14:11:34.408000 1820 UserTrace BIP2638I: MQPUT to queue 'IssuerefundCheck.Failure' on queue manager 'WMQI': MQCC=0, MQRC=0; node 'IssuerefundCheck.IssuerefundCheckFailure'.
The node 'IssuerefundCheck.IssuerefundCheckFailure' attempted to write a message to the specified queue 'IssuerefundCheck.Failure' connected to queue manager 'WMQI'. The MQCC was 0 and the MQRC was 0.
No user action required.
2003-07-18 14:11:34.408000 1820 UserTrace BIP2622I: Message successfully output by output node 'IssuerefundCheck.IssuerefundCheckFailure' to queue 'IssuerefundCheck.Failure' on queue manager 'WMQI'.
The MQSeries output node 'IssuerefundCheck.IssuerefundCheckFailure' successfully wrote an output message to the specified queue IssuerefundCheck.Failure connected to queue manager WMQI.
No user action required.
2003-07-18 14:11:44.613998 760 UserTrace BIP2632I: Message being propagated to the output terminal; node 'ConfigurationMessageFlow.InputNode'.
An input message received from MQSeries input queue in node 'ConfigurationMessageFlow.InputNode' is being propagated to any nodes connected to the output terminal.
No user action required.
2003-07-18 14:11:44.613998 760 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
The message broker has created a parser of type 'Properties' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle the first part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '0' bytes long.
No user action required.
2003-07-18 14:11:44.613998 760 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
The message broker has created a parser of type 'MQMD' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '0' and '364' bytes long. This parser type was selected as the best match given the value 'MQHMD' from the previous parser.
No user action required.
2003-07-18 14:11:44.613998 760 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '227' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
The message broker has created a parser of type 'XML' on behalf of node 'ConfigurationMessageFlow.InputNode' to handle a subsequent part of an incoming message. This parser has been given the portion of the message starting at offset '364' and '227' bytes long. This parser type was selected as the best match given the value 'XML' from the previous parser.
No user action required. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Jul 18, 2003 11:45 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You are not capturing, or presenting, the exception list that would indicate the real cause of the failure. The log entries you have shown occur as the failure terminal of your MQInput node is being called because the message has been backed out to the input queue more times than the backout count on the queue specifies. By the time the failure terminal is called, the original exception is lost.
You either need to show more of the trace log, from before this message, or add tracing to the Catch terminal of your input node in order to capture the ExceptionList.
Also, most people find it confusing if the same question is posted in two forums. |
|
| Back to top |
|
|
| j1 |
| Posted: Sun Jul 20, 2003 3:37 pm Post subject: |
|
|
Centurion
Joined: 23 Jun 2003
Posts: 139
|
| sorry abt posting it in two places. I will delete it from the other place |
|
| 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
|
|
|
|
