MQSeries.net :: View topic - Need more help from Experts, regarding the COD problem

kvnathan · Posted: Wed Nov 28, 2001 5:13 am Post subject:

As we said earlier about the problem in getting the COD from the other end, I am just explaining once again the current scenario of the problem exixts.
In our java program we have to set the applicationIdData for some type of messages we are going to send. So for that we added the following code
-------------------------------------
int openoptions = MQC.MQOO_OUTPUT | MQC.MQOO_SET_IDENTITY_CONTEXT;
queueobj = QMGR.accessQueue(sQueueName,openoptions,null,null,null);
.
.
MQPutMessageOptions pmo = new MQPutMessageOptions();
pmo.options = MQC.MQOO_SET_IDENTITY_CONTEXT ;
.
.
msg.applicationIdData = "AppIdData";
.
.
---------------------------------------
If we send the message by the above set option, we are getting the 2063 error. But if we send the message without the applicationIdData and without setting the MQC.MQOO_SET_IDENTITY_CONTEXT option, we are getting both the COA and COD in the specified Queue.

If we set the MQC.MQOO_SET_IDENTITY_CONTEXT option for applicationIdData we are getting the following error message.
------------------------------------------
AMQ7310: Report message could not be put on a reply-to queue.

EXPLANATION:
The attempt to put a report message on queue COACOD.LISTEN on
queue manager TESTQMGR failed with reason code 2063. The message will be
put on the dead-letter queue.
------------------------------------------
Please Clarify regarding this and tell us how to go about this problem. And for your information that we have created Queuemanager and Queues from our login(mqm member login) itself.

As kolban Said
---------------
1. Run the program as a user which is a member of the mqm group
2. Explicitly create a new privaleged group, make the user a member of the group and uset setmqaut to add that group to the target queue.

We are running the program as a user which is a member of the mqm group and it is the same user where we have created QueueManager and Queues.

And as Bduncan Said
--------------------
Another possibility is that (depending on the API you're using) when you tell the queue manager you want to set the context fields of the message, and you pass in the MQMD structure you have built up, it *may* treat any fields you never set as being "". In other words, while you only want to set the ApplicId field, other fields like ReplyToQMgr name, userid, etc., may be getting left blank because you are overriding the default values that the queue manager would have set by using the set context parameter. You may want to browse the messages you are putting and see if any fields in the MQMD that should be populated are being left blank, and then compare this result to the MQMDs that you get when you comment out the set context parameter...

After the message is put into the Queue, We browsed the message and the ReplytoQ and ReplytoQmgr is properly set. But when the other end get the message from the Queue, the COD is going to the Dead Letter Queue of that Queue Manager. Then we browsed the DeadLetter Queue and we found that the ReplytoQ is blank and ReplytoQmgr is not our QueueManager.

How to solve this problem ? All the operation we are doing in the user which is a member of the mqm group. Can we think of any other alternative solution behind this COD problem.
Please help us.

Thanks in advance.

Nathan