| Author |
Message
|
| chris boehnke |
 Posted: Mon Nov 09, 2009 11:45 am Post subject: reason code 2042 |
 |
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
Hi Guys,
We have our application getting messages from a Mainframe queue manager. When they try getting messages they are getting 2042 reason code.
I checked the MQ Options and found that application is using MQOO_INPUT_SHARED. I am not sure what else is causing this error.
MQ version 6.0.2.0, z/OS
can you guys throw some light on this. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Nov 09, 2009 12:17 pm Post subject: Re: reason code 2042 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| chris boehnke wrote: |
| I checked the MQ Options and found that application is using MQOO_INPUT_SHARED. I am not sure what else is causing this error. |
Another application using input exclusive? (Though frankly I'd have expected a different reason code for that). Something else accessing the queue? Have you checked the queue or just the application that's supposed to be using the queue?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| chris boehnke |
| Posted: Mon Nov 09, 2009 12:54 pm Post subject: Re: reason code 2042 |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
| Vitor wrote: |
| chris boehnke wrote: |
| I checked the MQ Options and found that application is using MQOO_INPUT_SHARED. I am not sure what else is causing this error. |
Another application using input exclusive? (Though frankly I'd have expected a different reason code for that). Something else accessing the queue? Have you checked the queue or just the application that's supposed to be using the queue? |
I checked with only application and the options are shared.
Is there a possibility like application got disconnected accidently and trying to open the same queue again and getting 2042? |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 09, 2009 1:08 pm Post subject: Re: reason code 2042 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| chris boehnke wrote: |
| Is there a possibility like application got disconnected accidently and trying to open the same queue again and getting 2042? |
Yes.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| chris boehnke |
| Posted: Mon Nov 09, 2009 1:11 pm Post subject: |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
| So, is restarting the application only the solution ? |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 09, 2009 1:13 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| chris boehnke wrote: |
| So, is restarting the application only the solution ? |
I'd doubt that would help - it's the WMQ side that think the object is in use, hence it's passing a reason code back to the app. You need to release the object.
The first step is finding out what's using it. Or what the queue manager thinks is using it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
