|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
2033 |
« View previous topic :: View next topic » |
Author |
Message
|
Prahasith |
Posted: Wed Jul 02, 2003 11:11 am Post subject: 2033 |
|
|
 Disciple
Joined: 16 May 2003 Posts: 184 Location: Kansas City
|
Hi all
what steps should be taken when we get a RC 2033
how do I troubleshoot it
thank you
prahasith |
|
Back to top |
|
 |
mqonnet |
Posted: Wed Jul 02, 2003 11:16 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
Depends upon what your requirement is.
If your requirement is to GET a message for sure, then you need to loop when you get a 2033. If your application should do nothing, then exit.
Troubleshoot???? What do you mean.
You get a 2033 when there are NO Committed messages on queue that are available to be retrieved. So, there is nothing much that you can do, other than coding your app to take care of such a situation.
Cheers
Kumar |
|
Back to top |
|
 |
Prahasith |
Posted: Wed Jul 02, 2003 11:20 am Post subject: hi |
|
|
 Disciple
Joined: 16 May 2003 Posts: 184 Location: Kansas City
|
how do i do that in application code
what kind of options do i have |
|
Back to top |
|
 |
mqonnet |
Posted: Wed Jul 02, 2003 11:42 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
just code RC==2033. or RC==MQRC_NO_MSG_AVAILABLE, do whatever you want. Where RC is the reason code from your get in the app.
Check one of the samples that should give you more idea.
If that doesnt help, be more precise of what you want. Check out few samples from the repository on this site too.
Cheers
Kumar |
|
Back to top |
|
 |
bduncan |
Posted: Wed Jul 02, 2003 4:23 pm Post subject: |
|
|
Padawan
Joined: 11 Apr 2001 Posts: 1554 Location: Silicon Valley
|
Depending on the specific requirements of system, a 2033 may be perfectly acceptable. For instance, if you have a long running application polling a queue for incoming messages, then it is going to constantly be getting 2033 "errors" - unless of course the application can't process messages as fast as they are coming onto the queue, but in that case you have bigger problems to worry about
Usually, you'll have a while loop which looks something like this:
Code: |
while (compcode == 0 AND (reason == 0 OR reason == 2033) {
message = MQGET();
}
|
Imagine we are doing the above MQGET with a 5 second wait interval. It means we will wait for a message to arrive on the queue for 5 seconds. If 5 seconds pass and we don't get a message, the call will return with a 2033. But since we are a long running process, we just ignore the 2033 and try again. _________________ Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
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
|
|
|
|