|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
WMQI 2.1 ExceptionList handling in Compute node |
« View previous topic :: View next topic » |
Author |
Message
|
MVO |
Posted: Wed Oct 16, 2002 6:59 am Post subject: WMQI 2.1 ExceptionList handling in Compute node |
|
|
 Centurion
Joined: 09 Sep 2001 Posts: 131
|
Hi,
It looks like we cannot porperly reference InputExceptionList in a Compute node any more. Example:
My trace node shows an ExceptionList as follows:
ExceptionList.RecoverableException.ParserException with some data
In the Compute node I have this statement:
if InputExceptionList.RecoverableException.ParserException IS NOT NULL then...
results in a FALSE value.
It has always worked under MQSI 2.0.2.
Anyone encountered the same problem ?
Thanks
 |
|
Back to top |
|
 |
kirani |
Posted: Wed Oct 16, 2002 9:09 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
MVO,
Have you checked with CARDINALITY function? For example,
Code: |
IF (CARDINALITY(InputExceptionList.RecoverableException.ParserException[]) > 0) THEN
-- Do something ...
END IF;
|
_________________ 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 |
|
 |
MVO |
Posted: Thu Oct 17, 2002 5:50 am Post subject: |
|
|
 Centurion
Joined: 09 Sep 2001 Posts: 131
|
Yes, CARDINALITY works fine. However, I have to modify my message flows to replace all check NULL condition with check CARDINALITY>0 when I upgrade from MQSI 2.0.2 to WMQI 2.1.
Just wonder if this is a bug in WMQI 2.1.
Thanks Kiran. |
|
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
|
|
|
|