| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Not able to browse a Q |
« View previous topic :: View next topic » |
| Author |
Message
|
| itsme_001 |
 Posted: Thu Feb 19, 2009 11:35 pm Post subject: Not able to browse a Q |
 |
|
Disciple
Joined: 02 Feb 2009
Posts: 157
|
here is the error msg I'm getting while trying to browse a local Q
MQOPEN - 'MQ_QMGR
MQGET 1, failed with CompCode:1 Reason:2080
MQCLOSE
MQDISC
Is it anything to do with the settings of Local Q authorities? |
|
| Back to top |
|
 |
| zpat |
| Posted: Fri Feb 20, 2009 12:08 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5867
Location: UK
|
Why don't you look up the reason code?
| Quote: |
Reason Code 2080 x'820'
MQRC_TRUNCATED_MSG_FAILED
On an MQGET call, the message length was too large to fit into the supplied buffer. The MQGMO_ACCEPT_TRUNCATED_MSG option was not specified, so the message has not been removed from the queue. If this was a browse operation, the browse cursor remains where it was before this call, but if MQGMO_BROWSE_FIRST was specified, the browse cursor is positioned logically before the highest-priority message on the queue. The DataLength field is set to the length of the message before truncation, the Buffer parameter contains as much of the message as fits, and the MQMD structure is filled in.
Corrective action: Supply a buffer that is at least as large as DataLength, or specify MQGMO_ACCEPT_TRUNCATED_MSG if not all of the message data is required. |
|
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 20, 2009 12:11 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 20, 2009 12:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zpat wrote: |
Why don't you look up the reason code?
| Quote: |
Reason Code 2080 x'820'
MQRC_TRUNCATED_MSG_FAILED
On an MQGET call, the message length was too large to fit into the supplied buffer. The MQGMO_ACCEPT_TRUNCATED_MSG option was not specified, so the message has not been removed from the queue. If this was a browse operation, the browse cursor remains where it was before this call, but if MQGMO_BROWSE_FIRST was specified, the browse cursor is positioned logically before the highest-priority message on the queue. The DataLength field is set to the length of the message before truncation, the Buffer parameter contains as much of the message as fits, and the MQMD structure is filled in.
Corrective action: Supply a buffer that is at least as large as DataLength, or specify MQGMO_ACCEPT_TRUNCATED_MSG if not all of the message data is required. |
|
So not just me spoiling the fishing then....?
http://www.mqseries.net/phpBB2/viewtopic.php?t=47806
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| itsme_001 |
| Posted: Fri Feb 20, 2009 12:15 am Post subject: |
|
|
Disciple
Joined: 02 Feb 2009
Posts: 157
|
|
| 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
|
|
|
|
