MQSeries.net :: View topic

cicsprog · Posted: Thu Oct 10, 2002 9:13 am Post subject: MQ CLient 2018 2019

Below is a description from my application folks on a problem they are having. NT 5.2 Client to OS/390 MQ v2.1. Anybody have an idea? Connection TIMEOUT?

Application has what it thinks is a valid connection to MQ. Within application we maintain a list of the object handles of the queues we have open. This means that within the application configuration there are generally 5 opens we have an object handle for. Sometimes the same queue can be opened more than once by a single desktop. We, the application, don't see them as open queues but rather a resource the client is trying to use. For instance, resource 'A' and resource 'B' might be the same queue. If the client needs to send to resource A, we open the resource and do a 'Put'. If the client needs to send to resource B, we open the resource and do the 'Put'. If A and B are the same queue, we would open the queue 2 times and maintain a separate object handle for A and B.

In the case where messages are ending up on the wrong queue we're not sure what triggers it , but what we do see is that when we, application has received a message from the client for us to send, we look in our list of 'open' resources and if we have that resource open we use the handle and do the 'Put'. From our perspective, the PUT has worked - we got zero return codes, however when we turn around and do the GET we receive the 2019 or 2018 error, using the same handle. Upon further investigation, we also discovered that the message that was PUT earlier, if fact ended up on the wrong queue.