Team,

We have an Informatica cloud connector for IBMMQ, The connector reads messages from the Queue and writes to the queue.

in our connector, we have code to connect to Queue Manager and Queue.

when we run a read/ write task, it opens 2 connections.

before executing the task, the Queue manager connection count was 24, when we started executing the task Queue manager connection count increased by 2. (26)

In our case Queue Manager Name is "QM_Remote" and it has Queue "QA.QUEUE.1"

we have created a connector task to read messages from Queue "QA.QUEUE.1"

when the task executing Queue Manager Connection count increased by 2 and "QA.QUEUE.1" open output count is 0

instead of "QA.QUEUE.1" queue, " SYSTEM.ADMIN.COMMAND.QUEUE" open output count increased by 2

we expected this behavior for queue QA.QUEUE.1 but open output count increased for
"SYSTEM.ADMIN.COMMAND.QUEUE"

we would like to know why this is happening.

And in our connector, we added code to close the queue manager and queue but the connection is not closing.

even after the task complete, Queue Manager and Queue ""SYSTEM.ADMIN.COMMAND.QUEUE" connection count remains the same. its not closing

------------------------------
kumara rajasekar
------------------------------

Hi Kumara,

Make sure that you are absolutely certain that the increase of the open output count on the SYSTEM.ADMIN.COMMAND.QUEUE is coming from your application. You mention in your thread that you are using MQ Explorer to view what is happening. In order for MQ Explorer to show you what is happening, it will be using the SYSTEM.ADMIN.COMMAND.QUEUE.

To see what your application, and not other applications such as MQ Explorer, is doing, make use of the Application Connections view. To see it, right click on the queue manager in the MQ Explorer Navigator and choose "Application Connections..."

In the window that is opened as a result of this action, in the top half of the window, find your application and select it, and then the lower half of the window will show all the object handles (that is opened queues) that this application is using. In the screenshot below I have demonstrated this by selected the MQ Explorer application so you can see that it uses the SYSTEM.ADMIN.COMMAND.QUEUE. Your application will show other queues.

If, alternatively you want to view the SYSTEM.ADMIN.COMMAND.QUEUE and see who is using it, you can instead do the following. Right-click on the Queues folder in the MQ Explorer Navigator and choose "Status..."

In the window that is opened as a result of this action, in the top half of the window, find the SYSTEM.ADMIN.COMMAND.QUEUE and select it. The bottom half of the window will show the various applications that have this queue open. You will see MQ Explorer with it open for output and the IBM MQ Command Server task of the queue manager (amqpcsea.exe) with it open for input. You may see others (as in my screen shot) depending on what MQ admin tools you are using. Now you can check whether your application is using it or not. I expect you will find that it is not.

I hope that helps.

Cheers,
Morag

------------------------------
Morag Hughson
MQ Technical Education Specialist
MQGem Software Limited
Website: https://www.mqgem.com
------------------------------

Hi again Kumara,

In addition to my earlier reply I just want to add something else.

You said: we have created a connector task to read messages from Queue "QA.QUEUE.1"

This means you should be looking at the open input count and not the open output count. The open output count shows applications that are using a queue to write to it. You said you are using a queue to read from. This will be counted in the "open input count".

Cheers,
Morag

------------------------------
Morag Hughson
MQ Technical Education Specialist
MQGem Software Limited
Website: https://www.mqgem.com
------------------------------