| Author |
Message
|
| 9A5YY |
 Posted: Mon May 19, 2025 3:46 am Post subject: CCDT and WAS CONNAME |
 |
|
Centurion
Joined: 27 Sep 2005
Posts: 105
Location: Croatia
|
Hello!
Does anybody have experience at Linux to connect WAS to queue managers using CCDT file. I tried to do test connection in WAS connection factory and I received RC 2278. In CCDT file is only one queue manager.
The same CCDT file is used at my PC. I tested CCDT file using amqsputc and runmqsc -c commands. Without any problem I was succesfully connected to the qmgr with runmqsc -c and amqsputc.
Does anybody have idea what to do here to connect WAS to qmgr using CCDT?
Regards |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon May 19, 2025 9:57 am Post subject: Re: CCDT and WAS |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| 9A5YY wrote: |
Hello!
Does anybody have experience at Linux to connect WAS to queue managers using CCDT file. I tried to do test connection in WAS connection factory and I received RC 2278. In CCDT file is only one queue manager.
The same CCDT file is used at my PC. I tested CCDT file using amqsputc and runmqsc -c commands. Without any problem I was succesfully connected to the qmgr with runmqsc -c and amqsputc.
Does anybody have idea what to do here to connect WAS to qmgr using CCDT?
Regards |
Remember the CCDT is a BINARY file
Make sure your path to the CCDT file is absolute.
What does your WAS error log show for the connection attempt?
What is your current setup for the CCDT:
| Code: |
runmqsc -n <CCDTfile>
dis chl(*) all
end
|
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| 9A5YY |
| Posted: Mon May 19, 2025 11:32 pm Post subject: |
|
|
Centurion
Joined: 27 Sep 2005
Posts: 105
Location: Croatia
|
Yes, the CCDT file is download binary to WAS Linux server.
Yes, the path for CCDT file is specified absolute at WAS.
In connection factory after connection attempt RC=2278 is showed.
Is there any WAS log where more messages can be found for connection attempt?
My current setup for CCDT is as follows:
D:\>runmqsc -n
5724-H72 (C) Copyright IBM Corp. 1994, 2022.
Starting local MQSC for 'AMQCLCHL.TAB'.
dis chl(*) all
1 : dis chl(*) all
AMQ8414I: Display Channel details.
CHANNEL(CHL_NAME) CHLTYPE(CLNTCONN)
AFFINITY(PREFERRED) ALTDATE(2025-05-19)
ALTTIME(08.32.50) CERTLABL( )
CLNTWGHT(0) COMPHDR(NONE)
COMPMSG(NONE)
CONNAME(IP1 (1414), IP2 (1414))
DEFRECON(NO) DESCR( )
HBINT(300) KAINT(AUTO)
LOCLADDR( ) MAXMSGL(4194304)
MODENAME( ) PASSWORD( )
QMNAME(QMGR_NAME) RCVDATA( )
RCVEXIT( ) SCYDATA( )
SCYEXIT( ) SENDDATA( )
SENDEXIT( ) SHARECNV(10)
SSLCIPH( ) SSLPEER( )
TPNAME( ) TRPTYPE(TCP)
USERID( )
AMQ8414I: Display Channel details.
CHANNEL(SYSTEM.DEF.CLNTCONN) CHLTYPE(CLNTCONN)
AFFINITY(PREFERRED) ALTDATE(2025-05-19)
ALTTIME(08.31.09) CERTLABL( )
CLNTWGHT(0) COMPHDR(NONE)
COMPMSG(NONE) CONNAME( )
DEFRECON(NO) DESCR( )
HBINT(300) KAINT(AUTO)
LOCLADDR( ) MAXMSGL(4194304)
MODENAME( ) PASSWORD( )
QMNAME( ) RCVDATA( )
RCVEXIT( ) SCYDATA( )
SCYEXIT( ) SENDDATA( )
SENDEXIT( ) SHARECNV(10)
SSLCIPH( ) SSLPEER( )
TPNAME( ) TRPTYPE(TCP)
USERID( )
end
2 : end
No commands have a syntax error.
Last edited by 9A5YY on Tue May 20, 2025 7:23 am; edited 1 time in total |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue May 20, 2025 5:18 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
How are you defining the connection factory to WAS?
Did you check that you could connect correctly using amqscnx and the CCDT?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| 9A5YY |
| Posted: Tue May 20, 2025 11:09 pm Post subject: |
|
|
Centurion
Joined: 27 Sep 2005
Posts: 105
Location: Croatia
|
I configured a connection factory for the WebSphere MQ messaging provider.
I had to select the connection method. The options are to use a client channel
definition table or to enter all the connection information via the wizard.
I selected CCDT. I was asked to provide the client channel definition table URL
and queue manager name.
The URL for the CCDT is:
file:///absolute_path/AMQCLCHL.TAB
After this I performed a test connection which failed.
I tested connection from my PC using these commands to test CCDT is it correct:
SET MQCHLLIB=CCDT_directory_path
SET MQCHLTAB=AMQCLCHL.TAB
amqsputc QUEUE_NAME QMGR_NAME
runmqsc -c QMGR_NAME
All works fine and I was connected.
I have never used amqscnx to check connectivity. I cannot find amqscnx.
I found in samp directory this:
amqscnxc [-x ConnName [-c SvrconnChlName]] [-u User] [QMgrName]
Do you suggest to use this command to check that I could connect correctly using amqscnxc and the CCDT? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed May 21, 2025 10:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| 9A5YY wrote: |
I configured a connection factory for the WebSphere MQ messaging provider.
I had to select the connection method. The options are to use a client channel
definition table or to enter all the connection information via the wizard.
I selected CCDT. I was asked to provide the client channel definition table URL
and queue manager name.
The URL for the CCDT is:
file:///absolute_path/AMQCLCHL.TAB
After this I performed a test connection which failed.
I tested connection from my PC using these commands to test CCDT is it correct:
SET MQCHLLIB=CCDT_directory_path
SET MQCHLTAB=AMQCLCHL.TAB
amqsputc QUEUE_NAME QMGR_NAME
runmqsc -c QMGR_NAME
All works fine and I was connected.
I have never used amqscnx to check connectivity. I cannot find amqscnx.
I found in samp directory this:
amqscnxc [-x ConnName [-c SvrconnChlName]] [-u User] [QMgrName]
Do you suggest to use this command to check that I could connect correctly using amqscnxc and the CCDT? |
Yes set the CCDT variables. Make sure there is not MQServer variable defined and use
| Code: |
| amqscnxc [-u user] QMgrName |
If you can connect this would mean the CCDT is right and you have to review how to define it to WAS. (You might have to go to the custom dialog).
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| 9A5YY |
| Posted: Wed May 21, 2025 10:37 pm Post subject: |
|
|
Centurion
Joined: 27 Sep 2005
Posts: 105
Location: Croatia
|
I tried with amqscnxc and connecting to the queue manager was successful.
SET MQCHLLIB=CCDT_directory_path
SET MQCHLTAB=AMQCLCHL.TAB
D:\>amqscnxc QMGR_NAME
Sample AMQSCNXC start
Connecting to queue manager QMGR_NAME
with no client connection information specified.
Connection established to queue manager QMGR_NAME
Sample AMQSCNXC end |
|
| Back to top |
|
|
| 9A5YY |
| Posted: Tue May 27, 2025 1:02 am Post subject: |
|
|
Centurion
Joined: 27 Sep 2005
Posts: 105
Location: Croatia
|
After I checked CCDT file, I specified in WAS panel:
file:///CCDT_directory_path/AMQCLCHL.TAB
queue manager: QMGR_NAME
I made connection test in WAS connection factory but I received RC 2538.
Does anybody have idea what to do here? |
|
| Back to top |
|
|
| 9A5YY |
| Posted: Thu Aug 07, 2025 1:47 am Post subject: |
|
|
Centurion
Joined: 27 Sep 2005
Posts: 105
Location: Croatia
|
Hello!
I solved problem in this way.
I removed all spaces in CONNAME in my CCDT file:
before
CONNAME(IP1 (1414), IP2 (1414))
now
CONNAME(IP1(1414),IP2(1414))
and created the new CCDT file.
After that WAS was connected to the MQ without any problem and test connection was successful.
Regards |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Aug 07, 2025 9:28 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9486
Location: US: west coast, almost. Otherwise, enroute.
|
Official IBM doc
https://www.ibm.com/docs/en/ibm-mq/9.2.x?topic=SSFKSJ_9.2.0/com.ibm.mq.ref.con.doc/q081820_.html says
| Quote: |
| Specify CONNAME as a comma-separated list of names of machines for the stated TRPTYPE. |
... but then offers an easily misunderstood and copied typo example with a space separating names.
| Quote: |
If the transport type is TCP
CONNAME is either the host name or the network address of the remote machine (or the local machine for cluster-receiver channels). For example, (ABC.EXAMPLE.COM), (2001:DB8:0:0:0:0:0:0) or (127.0.0.1). It can include the port number, for example (MACHINE(123)). |
Look carefully following (ABC.EXAMPLE.com), there is a single space before (2001...
(2001, a space oddysy)
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
