| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQInput CCDT connection |
« View previous topic :: View next topic » |
| Author |
Message
|
| Mandrake90 |
 Posted: Thu Apr 02, 2020 12:23 am Post subject: MQInput CCDT connection |
 |
|
Novice
Joined: 11 Feb 2020
Posts: 10
|
Hi all,
I'm getting troubles while reading messages from a remote Queue (MQ 9 version).
I configure my integration node side this way:
| Code: |
mqsireportproperties IIBNODE-o BrokerRegistry -r
mqsichangeproperties IIBNODE-o BrokerRegistry -n mqCCDT -v /IIBNODE/ssl/FOLDER1/QUEUENAME.TAB
mqsichangeproperties IIBNODE-o BrokerRegistry -n mqKeyRepository -v /IIBNODE/ssl/client_HOSTNAME
|
...and I reboot the node.
Later when I configure my MQInput Node on IIBv10 Using these params:
Basic: QueueName
[MQConnecrion] Connection: Client Channel Definition Table (CCDT)
Destination QM Name: QMNGR_NAME
Use SSL: Flagged
But reading logs I get this
| Code: |
Apr 1 18:37:09 HOSTNAMEBRKR user:err|error IIB[24183038]: IBM Integration Bus v10007 (LOCALQM.EXGRP) [Thread 6211] (Msg 2/2) BIP2690E: Failed to make a CCDT connection to queue manager 'QMNGR_NAME': MQCC=2; MQRC=2058.
|
Trying to browse the same queue by command line it works fine :
| Code: |
$ amqsgbrc QUEUENAME QMNGR_NAME
Sample AMQSGBR0 (browse) start
QMNGR_NAME
Messages for QUEUENAME
1 <Testing. >
2 <Test number 2 >
no more messages
Sample AMQSGBR0 (browse) end
|
I hope you have all information you need and the patience to help me to solve the mistery  [/quote] |
|
| Back to top |
|
 |
| exerk |
| Posted: Thu Apr 02, 2020 8:43 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
MQRC 2058 is Q_MGR_NAME_ERROR, so are you absolutely sure the Broker flow is supplying the correct queue manager name?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Apr 02, 2020 2:31 pm Post subject: |
|
|
Jedi
Joined: 25 Mar 2003
Posts: 2494
Location: Melbourne, Australia
|
And sure that the qmgr name is defined in CCDT file /IIBNODE/ssl/FOLDER1/QUEUENAME.TAB ?
amqsgbrc is not necessarily going to use the same method to determine the MQ client connection details as the IIB message flow.
_________________
Glenn |
|
| Back to top |
|
|
| hughson |
| Posted: Thu Apr 02, 2020 4:43 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
MQRC_Q_MGR_NAME_ERROR (2058) means that the application did not find that queue manager name in the QMNAME field in any record in the CCDT.
Check the CCDT to ensure that the QMNAME field in the appropriate record in the CCDT does contain the same queue manager name that the application is using.
To do this, set MQCHLLIB and MQCHLTAB environment variables, then use runmqsc -n, and issue DISPLAY CHANNEL(*) ALL.
If the CCDT is all correct, then MQRC_Q_MGR_NAME_ERROR (2058) means that the application did not find the CCDT file to read at all and is reporting that there is no local queue manager of that name.
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
