Author |
Message
|
jj |
Posted: Thu Apr 10, 2008 4:11 am Post subject: MQ6 - error codes lost... |
|
|
Newbie
Joined: 09 Apr 2008 Posts: 6
|
I have a .Net application which reads messages from IBM MQ. After we upgraded MQ from V5.3 to V6 all the exception messsages are lost. In the new environment all exceptions are raised as "Error in the application" - For example, the error message when the Queue Manager is not open "MQRC_Q_MGR_NOT_AVAILABLE:" now shows "Error in the application".
Any ideas why this happening? |
|
Back to top |
|
 |
tleichen |
Posted: Thu Apr 10, 2008 7:09 am Post subject: Re: MQ6 - error codes lost... |
|
|
Yatiri
Joined: 11 Apr 2005 Posts: 663 Location: Center of the USA
|
I made a routine similar to this on both the mainframe in assembler and on distributed in C++ several years ago. I'm not really into .NET, and without knowing anything more about your application, I can't say with any certainty what exactly the problem is. But if I were to venture a guess, you are using the standard include header files for the error codes to create a table that is traversed and matched up against the error code in question. If it does not find a match, it gives you a default of "Error in the application". I would examine those header files in both 5.3 and 6.0 and the logic in that routine to determine any structural changes that may be causing your routine to fail.  _________________ IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
Back to top |
|
 |
jj |
Posted: Thu Apr 10, 2008 9:14 am Post subject: |
|
|
Newbie
Joined: 09 Apr 2008 Posts: 6
|
I will take a look.
As a note, I haven't changed anything on the application, only the IBM MQ was upgraded.
thanks. |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Apr 10, 2008 9:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I wonder if the application was correctly reporting the right things in the first place... or if it was merely taking advantage of an undocumented feature in the v5.3 classes. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
tleichen |
Posted: Thu Apr 10, 2008 3:08 pm Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005 Posts: 663 Location: Center of the USA
|
Either way, someone needs to understand how the parts are put together if you're going to solve this.  _________________ IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
Back to top |
|
 |
vantones |
Posted: Wed Apr 16, 2008 4:36 am Post subject: |
|
|
Newbie
Joined: 16 Apr 2008 Posts: 1
|
You are not alone... I have also just upgraded from 5.3 to 6.0 since it is far more robust on some other parts while beingused with .NET. The error messages are lost and we also just get "Error in the application." - errors. Did you get to shed some light on this or does anyone have any ideas on this? I'm fumbling in the dark...  |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Apr 16, 2008 2:22 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Did you guys specifically update your version of mqdlls in M$ gstoolkit (or whatever the global memory cache for dlls is called these days)? _________________ MQ & Broker admin |
|
Back to top |
|
 |
jj |
Posted: Thu Apr 17, 2008 1:00 pm Post subject: |
|
|
Newbie
Joined: 09 Apr 2008 Posts: 6
|
From the .Net application point of view I didn't change anything. |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Apr 17, 2008 6:20 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
In this case you may have an obsolete dll in the cache.
M$ documented how to load a dll to the chache and how to unload it...
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|