Author |
Message
|
newcall |
Posted: Wed Nov 27, 2002 12:38 am Post subject: message flow exception handling |
|
|
Newbie
Joined: 27 Nov 2002 Posts: 1
|
hi
i have developed a message flow which converts xml to mrm. In the mrm, i have field name which is 10 characters in length. If the length is > or < 10, the compute node is throwing an error. I want to use a try/catch block but i dont know where to write the logic to know that the error has occured for the specified field - name. please help me. is there anything in mqsi which tells you about this error ? |
|
Back to top |
|
 |
amigupta1978 |
Posted: Wed Nov 27, 2002 1:35 am Post subject: |
|
|
Centurion
Joined: 22 Jan 2002 Posts: 132 Location: India
|
Hi,
U can use the following set of things
USe try-catch node before Compute node. Then connect Try terminal to compute node and catch terminal where u will handle the exception.
Whenever any exception is thrown in MQSI it creates a tree ExceptionList. U can get feel of it if u connect a Trace node to the catch terminal and write the following pattern ${ExceptionList}
and then u can see how to handle the exceptions.
Regards,
Amit _________________ IBM certified MQseries Specialist
IBM certified WMQI Specialist |
|
Back to top |
|
 |
lung |
Posted: Wed Nov 27, 2002 4:58 pm Post subject: |
|
|
 Master
Joined: 27 Aug 2002 Posts: 291 Location: Malaysia
|
If the length is more than the length defined in your MRM, it will return an exception.
But I wasn't aware that if the length is less, it will return an exception as well... I have messages in which the field length is less than the length defined in my MRM, and it gives me no exception  _________________ lung |
|
Back to top |
|
 |
kirani |
Posted: Wed Nov 27, 2002 9:30 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
Lung,
Could you tell us more about the properties set in MRM for this element? _________________ 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 |
|
 |
lung |
Posted: Thu Nov 28, 2002 1:50 am Post subject: |
|
|
 Master
Joined: 27 Aug 2002 Posts: 291 Location: Malaysia
|
I was talking about converting pure XML messages to MRM-XML. If I'm trying to convert a host message to MRM-CWF, then definitely the length will need to be the same.
Anyway, which element are you asking about, Kiran?
 _________________ lung |
|
Back to top |
|
 |
kwelch |
Posted: Mon Dec 02, 2002 12:03 pm Post subject: |
|
|
 Master
Joined: 16 May 2001 Posts: 255
|
If the field in the MRM is defined as 10 I believe it expects 10 exactly, no less no more. For those less, you can define padding character of space in the CWF tab. For those greater you can use substring to get the 10 bytes you want.
Karen |
|
Back to top |
|
 |
lung |
Posted: Mon Dec 02, 2002 9:54 pm Post subject: |
|
|
 Master
Joined: 27 Aug 2002 Posts: 291 Location: Malaysia
|
Quote: |
If the field in the MRM is defined as 10 I believe it expects 10 exactly, no less no more. |
I think this is only true if you installed CSD03...  _________________ lung |
|
Back to top |
|
 |
kirani |
Posted: Mon Dec 02, 2002 9:57 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
Lung,
This is true even with lower version/CSD of MQSI/WMQI. As Karen said, if you have Element length assigned in CWF/TDS tabs, you have to send data of exact length. _________________ 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 |
|
 |
kwelch |
Posted: Tue Dec 03, 2002 7:02 am Post subject: |
|
|
 Master
Joined: 16 May 2001 Posts: 255
|
Hi Lung,
We don't have CSD3 installed yet.
Karen |
|
Back to top |
|
 |
lung |
Posted: Tue Dec 03, 2002 5:33 pm Post subject: |
|
|
 Master
Joined: 27 Aug 2002 Posts: 291 Location: Malaysia
|
Is it? Okay, thanks for the clarification  _________________ lung |
|
Back to top |
|
 |
|