| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Creating COBOL Message |
« View previous topic :: View next topic » |
| Author |
Message
|
| deepak_paul |
 Posted: Mon Apr 19, 2010 11:51 am Post subject: Creating COBOL Message |
 |
|
Centurion
Joined: 04 Oct 2008
Posts: 147
Location: US
|
All,
When we are creating Cobol message, i am getting belw errror messages.
| Code: |
2010-04-19 12:06:51.278440 2235 UserTrace BIP5494I: The logical tree is now being matched to the message model.
2010-04-19 12:06:51.278508 2235 UserTrace BIP5564I: Item ''CU_XOUT_DATA_AREA'' from the logical tree has matched with the message model as ''[MESSAGE]_msg_CUWXCALPASSAREA/CU_XOUT_DATA_AREA''.
2010-04-19 12:06:51.278560 2235 UserTrace BIP5564I: Item ''CU_XOUT_ACCT_ADDR_DETAIL_AREA'' from the logical tree has matched with the message model as ''[MESSAGE]_msg_CUWXCALPASSAREA/CU_XOUT_DATA_AREA/[CHOICE]/CU_XOUT_ACCT_ADDR_DETAIL_AREA''.
2010-04-19 12:06:51.278636 2235 UserTrace BIP5564I: Item ''CU_XOUT_RESULTS_X'' from the logical tree has matched with the message model as ''[MESSAGE]_msg_CUWXCALPASSAREA/CU_XOUT_DATA_AREA/[CHOICE]/CU_XOUT_ACCT_ADDR_DETAIL_AREA/[SELF_DEFINING]''.
2010-04-19 12:06:51.278684 2235 UserTrace BIP5493W: Message, element or attribute 'CU_XOUT_RESULTS_X' is self-defining within parent 'CU_XOUT_DATA_AREA'. The message, element or attribute 'CU_XOUT_RESULTS_X' did not match with any corresponding artifact in the message model hence it is considered to be self-defining.
If it is not intended that this message, element or attribute be self-defining,
check that the message set is referenced in the message properties, or
modify the message model to correspond to the instance message, or
modify the instance message to correspond to the message model.
2010-04-19 12:06:51.280048 2235 Error BIP2628E: Exception condition detected on input node 'XML2COBOL.MQInput'.
The input node 'XML2COBOL.MQInput' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2010-04-19 12:06:51.280056 2235 RecoverableException BIP2230E: Error detected whilst processing a message in node 'XML2COBOL.MQOutput'.
The message broker detected an error whilst processing a message in node 'XML2COBOL.MQOutput'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2010-04-19 12:06:51.280064 2235 ParserException BIP5286E: Writing errors have occurred. Message set name: 'CUWCALL' Message format: 'Binary1' Message type path: '/msg_CUWXCALPASSAREA'
Review other error messages to find the cause of the errors.
2010-04-19 12:06:51.280068 2235 ParserException BIP5167E: A Custom Wire Format error occurred during the parsing or writing of message ''msg_CUWXCALPASSAREA''.
See the following messages for further details. Contact your IBM support center if you cannot resolve the error.
2010-04-19 12:06:51.280076 2235 ParserException BIP5350E: There was a Custom Wire Format error when writing the message ''msg_CUWXCALPASSAREA''. The error occurred during or after the writing of element ''/msg_CUWXCALPASSAREA/CU_XOUT_DATA_AREA/CU_XOUT_ACCT_ADDR_DETAIL_AREA''.
Check that the message has been built correctly and conforms to the MRM model.
Review other error messages for more details.
2010-04-19 12:06:51.280084 2235 ParserException BIP5345E: CWF Worker: The tree contains an illegal choice element. Message name: ''msg_CUWXCALPASSAREA'' Element name: ''UNDEFINED''
The CWF worker cannot handle certain types of elements (those for which the length depends on the actual value of the message) within a 'choice' element. This error indicates that the CWF Worker has encountered such elements and cannot proceed with parsing or writing.
Redesign the message in question so that its 'choice' elements do not contain length/repeat references or the illegal physical types (null, null terminated string, length encoded string 1 and length encoded string 2) or use a different wire format.
2010-04-19 12:06:52.281784 2235 Error BIP2648E: Message backed out to a queue; node 'XML2COBOL.MQInput'. |
In Cobol Copy Book:.. one of my fields is like below.
.
.
10 CU-XOUT-RESULTS-X
057900 REDEFINES CU-XOUT-RESULTS PIC X(02).
.
.
Thanks
Paul
_________________
Regards
Paul |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Apr 19, 2010 12:52 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If you're using a REDEFINES, you'll probably need to tweak the message set if you used the import wizard.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| deepak_paul |
| Posted: Mon Apr 19, 2010 1:05 pm Post subject: |
|
|
Centurion
Joined: 04 Oct 2008
Posts: 147
Location: US
|
Vitor - Can you please tell me how exactly i need to tweak the message set?
_________________
Regards
Paul |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Apr 19, 2010 1:56 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| deepak_paul wrote: |
| Vitor - Can you please tell me how exactly i need to tweak the message set? |
A REDEFINES element doesn't have a direct equivalent in XML schema so the importer does the best it can. In this instance I'd say it's created both elements in a choice group and your bitstream doesn't match that.
If you think for a minute, you'll realise that the REDEFINES isn't valid when producing a COBOL message, because it doesn't reference a unique piece of storage. So you can't assign it in the message tree.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| deepak_paul |
| Posted: Mon Apr 19, 2010 2:22 pm Post subject: |
|
|
Centurion
Joined: 04 Oct 2008
Posts: 147
Location: US
|
Vitor,
What could be done now to get rid of this error?
_________________
Regards
Paul |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Apr 19, 2010 2:33 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I think the problem may be quite simple - the message tree does not match the message structure. Read the trace line by line ( and thanks for taking the user trace btw ) and you will see that
'CU_XOUT_DATA_AREA' was matched against an element '_msg_CUWXCALPASSAREA/CU_XOUT_DATA_AREA' in the message set
Clearly, CU_XOUT_DATA_AREA is the REDEFINEd element, because it contains a choice group. But that is not causing the problem, because the first child element in the message tree was 'CU_XOUT_ACCT_ADDR_DETAIL_AREA' and it was matched successfully against the message set as '[MESSAGE]_msg_CUWXCALPASSAREA/CU_XOUT_DATA_AREA/[CHOICE]/CU_XOUT_ACCT_ADDR_DETAIL_AREA'
The problem is with the first child of 'CU_XOUT_ACCT_ADDR_DETAIL_AREA' in the message tree. It did not match any child of 'CU_XOUT_ACCT_ADDR_DETAIL_AREA' and was therefore marked as self-defining. That's not always a problem, depending on the style of message that is being written out. In this case, it has to be a fatal error - you can't have undeclared data in the middle of a COBOL record because the receiver would have no idea how to parse it.
There is only one sure way to diagnose this: compare the message tree against the message set *very* carefully until you understand what the difference is, and then fix the message flow to make it produce a correct message tree.
I think the MRM parser is being quite helpful with the user trace messsages - in previous versions you had to start from the root and work all the way down. |
|
| 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
|
|
|
|
