| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQRC_DATA_LENGTH_ERROR |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Tue Jun 26, 2007 7:11 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
And you're quite certain (following my description earlier of how the default table is built) that the default object is entirely suitable for your use, and you don't need to follow my advice & create a tab file according to the documentation?
Well done spotting the problem, good luck with fixing it, maybe you have a permissions error on the file preventing the read.
Again, happy hunting. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| LordGladstone |
| Posted: Tue Jun 26, 2007 7:46 am Post subject: |
|
|
Novice
Joined: 07 Jun 2006
Posts: 19
|
| I have got the amqsputc working now, by taking the queue manager name out of the clnt chl definition. That is strange because it contradicts earlier advice. I will try the large message tomorrow. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jun 26, 2007 7:50 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Ok, so you've amended the default clnt conn to include a queue manager name. This is not good. Now you've changed it to blank, i.e. connect to any queue manager which is slightly unusual & will cause issues if you run the client in any environment with 2 queue manager due to prioritising rules.
But if you've got it working and you're happy well done you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
