MQ behavior in CICS and batch.

[Dhiraj]

Hello All,

We are using MQ for integration of transactions in batch and CICS.

Is there any difference between batch and online transaction setup? as we are getting good response when trying to get from Q (in case of Batch operation)

but in CICS transaction MQRC=2033. and not able to read response from Q. but can see that Q has responses.

what can be the reason? Please advise.

Thanks

!

Message from: Anuj Dhawan

Please Note: I split your post from the other post. Details are hidden, to avoid distraction, under the "SHOW SPOILER" button. For readers: This question is split from viewtopic.php?f=22&t=1839 for the following reason Hi Dhiraj, This seems to be a separate question than the original question in this thread. If yes, I'll make a separate thread for it for you and there we can discuss about it. Please advise. Yes Anuj, we can. Thanks, I was thinking that it's related and recent question what I had posted. If you want to change the Subject of this new thread, please state so in your reply and I'll do it for you.

[Anuj Dhawan]

Hi Dhiraj,

Please see if this helps:

Cause
The following are the most likely causes for MQRC 2033:
There are no messages on the queue.
The unit of work (UOW) for the MQPUT was not committed.
The messages have expired.
Resolving the problem
Consider this reason code as a normal condition and handle this condition in your getting application. Use the MQGET MQGMO_WAIT option and retry the MQGET.
The amqsget sample programs demonstrate the use of MQGET MQGMO_WAIT.

Verify that the putting application is committing the UOW. The current depth of the queue increments at MQPUT. However, messages are not available to the getting application until they are committed.
Messages that have expired will be counted in the current depth of the queue and they are discarded at the point of MQGET. Expired messages are never returned to the getting application. You may want to increase your message expiry time or use unlimited expiry for your messages.

Note: There are more reasons for MQRC 2033. This documents the most common causes.

The WebSphere MQ Application Programming Reference provides specific information regarding the MQ function calls and a list of Return codes.