| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Varied MQ Return Codes |
« View previous topic :: View next topic » |
| Author |
Message
|
| morfius9 |
 Posted: Wed May 23, 2007 11:01 pm Post subject: Varied MQ Return Codes |
 |
|
Novice
Joined: 06 May 2007
Posts: 13
|
hi,
I have an application that is putting messages to a queue. I brought down the queue manager associated with the same when this application was running and the return codes that i recieved are confusing.
1. 2085 - UNKNOWN OBJECT NAME initially.
2. 2161 - Queue Manager Quiecising
3. 2162 - Queue Manager Stopping all the time that the queue manager was down.
4. When i brought the queue manager up, i started recieving 2203 Connection Stopping return code. Finally i had to stop this program and restart it in CICS.
Can anyone help explain why this is happening?
Thanks, Morf |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed May 23, 2007 11:34 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I'd guess you had a temporary dynamic queue in there which deleted when the queue manager came down, hence the 2085.
The 2161/2162 codes are attempting to signal the closedown of the queue manager; your application should close in response.
The 2203 indicates your connection is stopping, because the queue manager instance you were connected to is stopping. As you've correctly determined, you need to reconnect to the running instance.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| morfius9 |
| Posted: Wed May 23, 2007 11:37 pm Post subject: |
|
|
Novice
Joined: 06 May 2007
Posts: 13
|
| Why is it giving me 2203 when the queue manager was again brought up? And all the time when im getting 2162, my queue manager was down for last one hour. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 24, 2007 12:25 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| morfius9 wrote: |
| Why is it giving me 2203 when the queue manager was again brought up? And all the time when im getting 2162, my queue manager was down for last one hour. |
You get a 2162 because there's no code for "stopped". The design expectation is that your program will bail on the first 2162, not sit there for an hour listening to more of them.
The 2203 has the same basic reason - it's a fatal "queue manager unconditionally stopping" which should cause your app to drop out. The queue manager which came back up is not the same instance that went down; different task id and so forth. The connection to that queue manager remains stopped.
It's for this reason the app should close when signalled that the queue manager is stopping (by whatever means).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu May 24, 2007 12:31 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| The moral of this story is to stop the CICS regions before stopping the queue manager (and vice versa). |
|
| Back to top |
|
|
| morfius9 |
| Posted: Mon May 28, 2007 12:24 am Post subject: |
|
|
Novice
Joined: 06 May 2007
Posts: 13
|
| Hmm....I get it now...I guess my program needs to be more efficient in handling this stuff. Thanks a lot guys for this eye opener. |
|
| 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
|
|
|
|
