Yea, Yea, I was in some wacky place in the barrels of coding. Yes, MQVE can
perform what Jan needs ;-) I just wanted to annoy a few of you about binary
and variable data, hehe.
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Roger
Lacroix
Sent: Tuesday, Marc
Title: Message
Kulbir:
There is nothing that will restrict you from having multiple brokers on a single
server except resources on that server. What has been done in a company I
am doing work at is to have client connections go through another server/qmgr so
no clients will directly con
Oh yes, I know this very well ;-)
Arg
You have to use the raw MQI structure/object for MQRFH2 and attach it to
your payload. It needs to be infront of it. After constructing your MQRFH2
header and writing it to your MQMessage object you can then add your normal
data/message to the MQMessage
Can you identify your WMQ version and OS, because you should not be limited
to 4mb with the latest WMQ.
I have written a lot of C++ WMQ programs that pass large amount of messages
and with segmentation or not have not had problems. Could you identify the
exact issues you are having.
Chris
Yes, the stored procedure sends back a return code and message associated
with a return code. The standard SQLCODE and SQLSTATE are not being passed
back though, so I lose out on retrieving the actual error. Due to this
reason we have designed it in a way that if an error occurs within the
stored
Title: Message
-Original Message-From: Christopher D. Fryett
Sent: Sunday, August 31, 2003 12:30 PMTo:
Subject: RE: Outsourcing - my observations after my trip to
India
Zafar:
Thank you for the detailed report you acquired from India. Although I
don't completely agree
If I recall correctly there is no event triggers for queue size, just depth.
If you are coming across an issue of queue size you may want to look at your
design again and validate you can support the message sizes for the queue
definitions you have. You may also need to review the method in how yo
Rainer,
Could you elaborate a little here. I would tend to think you would want
to use the backout/commit at a message level. So, when you commit a message
it is recognized in the target queue as visible and committed. You would
use the backout if an error of some sort you designated occurred
