Recently moved from the TAB file to using JSON but have had random issues with the client connection failing (have two MQ servers and the client JSON is defined to balance between the two). On one set of servers, this client erred for a couple of weeks and it just started working. On another set of servers, the client isn't working but the issue is random, sometimes it erred and sometimes it is successful. Not sure how to debug this. 

The JSON file is on the local file system, and the MQCHLIB and MQCHLTAB are set correctly. I am getting nothing in the log files. This is on Windows 2019 servers (the MQ server side is on Linux). 

Error  is MQRC_Q_MGR_NAME_ERROR. And I have validated the JSON against the schema. 

------------------------------
Kevin Cobb
------------------------------

Instead of using the qmgr name as provided in the JSON file for the connection, have you thought of using *qmgr for the connection when qmgr is provided in the JSON file? Works the same as the tab file worked in this reguard.

Did you check if you had any other queue manager set up with the same qmgr name in the JSON file (may be from copy/paste operations)?

------------------------------
Francois Brandelik

Original Message:
Sent: Wed October 25, 2023 10:01 AM
From: Kevin Cobb
Subject: CCDT JSON and Client Not Connecting

Recently moved from the TAB file to using JSON but have had random issues with the client connection failing (have two MQ servers and the client JSON is defined to balance between the two). On one set of servers, this client erred for a couple of weeks and it just started working. On another set of servers, the client isn't working but the issue is random, sometimes it erred and sometimes it is successful. Not sure how to debug this. 

The JSON file is on the local file system, and the MQCHLIB and MQCHLTAB are set correctly. I am getting nothing in the log files. This is on Windows 2019 servers (the MQ server side is on Linux). 

Error  is MQRC_Q_MGR_NAME_ERROR. And I have validated the JSON against the schema. 

------------------------------
Kevin Cobb
------------------------------

Recently moved from the TAB file to using JSON but have had random issues with the client connection failing (have two MQ servers and the client JSON is defined to balance between the two). On one set of servers, this client erred for a couple of weeks and it just started working. On another set of servers, the client isn't working but the issue is random, sometimes it erred and sometimes it is successful. Not sure how to debug this. 

The JSON file is on the local file system, and the MQCHLIB and MQCHLTAB are set correctly. I am getting nothing in the log files. This is on Windows 2019 servers (the MQ server side is on Linux). 

Error  is MQRC_Q_MGR_NAME_ERROR. And I have validated the JSON against the schema. 

------------------------------
Kevin Cobb
------------------------------

Hi Kevin,

The intermittent nature of the error you are seeing suggests that maybe only one of the two entries in the JSON CCDT has an error in it.

The error MQRC_Q_MGR_NAME_ERROR (2058) occurs when a client connection is being attempted and a CCDT is in use, if the provided queue manager name (i.e. the one you supply on the MQCONN(X) call, is not found as a QMNAME value in any of the entries in the CCDT. What value do you supply at MQCONN(X) time, and what value is in the QMNAME in each CCDT entry?

Is it possible for you to show us the contents of your JSON CCDT (perhaps with any private info redacted)?

Cheers,
Morag

Recently moved from the TAB file to using JSON but have had random issues with the client connection failing (have two MQ servers and the client JSON is defined to balance between the two). On one set of servers, this client erred for a couple of weeks and it just started working. On another set of servers, the client isn't working but the issue is random, sometimes it erred and sometimes it is successful. Not sure how to debug this. 

The JSON file is on the local file system, and the MQCHLIB and MQCHLTAB are set correctly. I am getting nothing in the log files. This is on Windows 2019 servers (the MQ server side is on Linux). 

Error  is MQRC_Q_MGR_NAME_ERROR. And I have validated the JSON against the schema. 

------------------------------
Kevin Cobb
------------------------------

Thanks for your suggestion. I checked the two connections in the CCDT JSON and they are correct. Also, the problem just seems to go away after a few days. I theorized that the problem is that the service user (windows machines) can't get the environment variables (MQCHLLIB and MQCHLTAB) and that somehow (machine reboot or service restart), eventually, they can. But not sure that theory agress with what you indicated as the underlying issue behind MQRC_Q_MGR_NAME_ERROR. Also, as I stated in the other reply, we are using *QMGR as the connection value for the "ClientConnectionChannelName", see below C# code. 

                var props = new Hashtable();
                props.Add(MQC.TRANSPORT_PROPERTY, MQC.TRANSPORT_MQSERIES_MANAGED);
                MqQueueManager = new MQQueueManager(smp.ClientConnectionChannelName, props);
 

Hi Kevin,

The intermittent nature of the error you are seeing suggests that maybe only one of the two entries in the JSON CCDT has an error in it.

The error MQRC_Q_MGR_NAME_ERROR (2058) occurs when a client connection is being attempted and a CCDT is in use, if the provided queue manager name (i.e. the one you supply on the MQCONN(X) call, is not found as a QMNAME value in any of the entries in the CCDT. What value do you supply at MQCONN(X) time, and what value is in the QMNAME in each CCDT entry?

Is it possible for you to show us the contents of your JSON CCDT (perhaps with any private info redacted)?

Cheers,
Morag

Recently moved from the TAB file to using JSON but have had random issues with the client connection failing (have two MQ servers and the client JSON is defined to balance between the two). On one set of servers, this client erred for a couple of weeks and it just started working. On another set of servers, the client isn't working but the issue is random, sometimes it erred and sometimes it is successful. Not sure how to debug this. 

The JSON file is on the local file system, and the MQCHLIB and MQCHLTAB are set correctly. I am getting nothing in the log files. This is on Windows 2019 servers (the MQ server side is on Linux). 

Error  is MQRC_Q_MGR_NAME_ERROR. And I have validated the JSON against the schema. 

------------------------------
Kevin Cobb
------------------------------

Kevin, 

Instead of using the environment variables, why can't they upload properties from an ini file and set the property on the queue manager

from memory

props.Add(WMQC.CCDT_URL, file:///pathtoJSonccdt.json)

where the Path and filename for the JSON ccdt would be retrieved from the application properties...

Thanks for your suggestion. I checked the two connections in the CCDT JSON and they are correct. Also, the problem just seems to go away after a few days. I theorized that the problem is that the service user (windows machines) can't get the environment variables (MQCHLLIB and MQCHLTAB) and that somehow (machine reboot or service restart), eventually, they can. But not sure that theory agress with what you indicated as the underlying issue behind MQRC_Q_MGR_NAME_ERROR. Also, as I stated in the other reply, we are using *QMGR as the connection value for the "ClientConnectionChannelName", see below C# code. 

                var props = new Hashtable();
                props.Add(MQC.TRANSPORT_PROPERTY, MQC.TRANSPORT_MQSERIES_MANAGED);
                MqQueueManager = new MQQueueManager(smp.ClientConnectionChannelName, props);
 

Hi Kevin,

The intermittent nature of the error you are seeing suggests that maybe only one of the two entries in the JSON CCDT has an error in it.

The error MQRC_Q_MGR_NAME_ERROR (2058) occurs when a client connection is being attempted and a CCDT is in use, if the provided queue manager name (i.e. the one you supply on the MQCONN(X) call, is not found as a QMNAME value in any of the entries in the CCDT. What value do you supply at MQCONN(X) time, and what value is in the QMNAME in each CCDT entry?

Is it possible for you to show us the contents of your JSON CCDT (perhaps with any private info redacted)?

Cheers,
Morag

Recently moved from the TAB file to using JSON but have had random issues with the client connection failing (have two MQ servers and the client JSON is defined to balance between the two). On one set of servers, this client erred for a couple of weeks and it just started working. On another set of servers, the client isn't working but the issue is random, sometimes it erred and sometimes it is successful. Not sure how to debug this. 

The JSON file is on the local file system, and the MQCHLIB and MQCHLTAB are set correctly. I am getting nothing in the log files. This is on Windows 2019 servers (the MQ server side is on Linux). 

Error  is MQRC_Q_MGR_NAME_ERROR. And I have validated the JSON against the schema. 

------------------------------
Kevin Cobb
------------------------------

Thanks for the suggestion. It's a good work around, but I don't see that property - WMQC.CCDT_URL. I did update the 'mqclient.ini' on the client side to include the path and JSON, and that also seems a good work around. Have not see the error since I added this section. Although, timing wise, it could be just a coincidence as this problem just goes away (my favorite kind). 

CHANNELS:
    ChannelDefinitionDirectory=PATH TO JSON
    ChannelDefinitionFile=JSON FILENAME

Kevin, 

Instead of using the environment variables, why can't they upload properties from an ini file and set the property on the queue manager

from memory

props.Add(WMQC.CCDT_URL, file:///pathtoJSonccdt.json)

where the Path and filename for the JSON ccdt would be retrieved from the application properties...

Thanks for your suggestion. I checked the two connections in the CCDT JSON and they are correct. Also, the problem just seems to go away after a few days. I theorized that the problem is that the service user (windows machines) can't get the environment variables (MQCHLLIB and MQCHLTAB) and that somehow (machine reboot or service restart), eventually, they can. But not sure that theory agress with what you indicated as the underlying issue behind MQRC_Q_MGR_NAME_ERROR. Also, as I stated in the other reply, we are using *QMGR as the connection value for the "ClientConnectionChannelName", see below C# code. 

                var props = new Hashtable();
                props.Add(MQC.TRANSPORT_PROPERTY, MQC.TRANSPORT_MQSERIES_MANAGED);
                MqQueueManager = new MQQueueManager(smp.ClientConnectionChannelName, props);
 

Hi Kevin,

The intermittent nature of the error you are seeing suggests that maybe only one of the two entries in the JSON CCDT has an error in it.

The error MQRC_Q_MGR_NAME_ERROR (2058) occurs when a client connection is being attempted and a CCDT is in use, if the provided queue manager name (i.e. the one you supply on the MQCONN(X) call, is not found as a QMNAME value in any of the entries in the CCDT. What value do you supply at MQCONN(X) time, and what value is in the QMNAME in each CCDT entry?

Is it possible for you to show us the contents of your JSON CCDT (perhaps with any private info redacted)?

Cheers,
Morag

Recently moved from the TAB file to using JSON but have had random issues with the client connection failing (have two MQ servers and the client JSON is defined to balance between the two). On one set of servers, this client erred for a couple of weeks and it just started working. On another set of servers, the client isn't working but the issue is random, sometimes it erred and sometimes it is successful. Not sure how to debug this. 

The JSON file is on the local file system, and the MQCHLIB and MQCHLTAB are set correctly. I am getting nothing in the log files. This is on Windows 2019 servers (the MQ server side is on Linux). 

Error  is MQRC_Q_MGR_NAME_ERROR. And I have validated the JSON against the schema. 

------------------------------
Kevin Cobb
------------------------------