| Author |
Message
|
| moresh |
 Posted: Wed Jan 30, 2008 9:04 am Post subject: Getting Reason Code 2010 on messages greater than 2 MB on MQ |
 |
|
Newbie
Joined: 30 Jan 2008
Posts: 2
|
Hi
I am using MQS to communicate messages between 2 applications. The MAXMSGL on Queue , Channel and Manager is defined to be 4MB
We can send messages upto 4 MB on the queue. However when we try to read a message greater than 2MB , it throws an 2010 error.
We were able to split the messages in batches of slightly less than 2 MB. Can any one advise on where the problem could be.
Thanks
Moresh |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jan 30, 2008 9:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Quote: |
MQRC_DATA_LENGTH_ERROR
Explanation:
The DataLength parameter is not valid. Either the parameter pointer is not valid, or it points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)
This reason can also be returned to an MQ client program on the MQGET, MQPUT, or MQPUT1 call, if the BufferLength parameter exceeds the maximum message size that was negotiated for the client channel.
Completion Code:
MQCC_FAILED
Programmer Response:
Correct the parameter.
If the error occurs for an MQ client program, also check that the maximum message size for the channel is big enough to accommodate the message being sent; if it is not big enough, increase the maximum message size for the channel. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| moresh |
| Posted: Wed Jan 30, 2008 9:19 am Post subject: |
|
|
Newbie
Joined: 30 Jan 2008
Posts: 2
|
Hi
I am using a 3rd party Application which uses MQS client to read the queue.
Where can i see the data length parameters or the bufferlenght parameter ?
Please advise.
Moresh |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 30, 2008 9:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You need to look at the client connection channel definition and the server connection channel definition.
Depending on what's being used, this may be the cause of the problem.
You should also look at both the version of the MQ Server and the version of the MQ Client install that the 3rd party app is using.
You should also raise this as an issue with the 3rd party app.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| MartynB |
| Posted: Thu Mar 20, 2008 7:59 am Post subject: 2010 issues... |
|
|
Novice
Joined: 14 Jan 2008
Posts: 24
|
Im having a similar issue against a mainframe queue manager I'm attempting to send a message to over MQClient.
The channel, queue and queue manager maxmsgl indicate enough capacity but I'm still getting @rsey: 2010.
Are there any underlying DASD issues on the mainframe I may need to be aware of? (excuse me if I have the incorrect terminology however I'm a windoze person myself).
I've tried this using two independant tools (although both written by myself). I'm using MQCONNX to connect. Are there and settings in the MQCD or MQPMO on the client that affect this behaviour?
Any assistance greatly recieved.
Regards,
Martyn |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 20, 2008 8:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You must be using a client connection table to do this.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Mar 20, 2008 8:42 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Are there any underlying DASD issues on the mainframe |
No.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Mar 24, 2008 11:42 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| The client channel max message size is defined at both the client and the queue manager side, the lowest value of the two is used. |
|
| Back to top |
|
|
|
|
