Stu,
One of the things that always bit me when first starting with client channel tables was the relationship between what queue manager name you specify (or donât specify) on your MQ Clients connection call versus how the CLNTCONN channels were built (which make up your client channel table).
If your client channel table has blanks for the QM name, but your app specifies the correct QM name, the connection will fail!!!
Do this: switch to using the amqscnxc sample app. All it does is connect to the QM, grab its name and disconnect. No complicating factors, the easiest way to identify if basic connectivity exists.
First do this:
amqscnxc -x YourServerName(Port#) -c YourChannelName
In this example, you are supplying the connection details. Get this to work and you prove that MQ Client is properly installed and network connectivity exists between you and the MQ server. You donât need to specify the QM name â there can only be one QM on a particular port and IP addresses, so the name is optional (when client channel tables are not involved)
Try again but give it the correct name: should work again.
amqscnxc -x YourServerName(Port#) -c YourChannelName YourQMName
Try again but give it the wrong name: should fail with 2058
amqscnxc -x YourServerName(Port#) -c YourChannelName WRONGNAME
Now try it omitting the âx and âc. This will cause the app to use the environment variables to get the connection details. â may work, may fail, depending how you built the client channel table.
amqscnxc
And again with the QM name â may work, may fail, depending how you built the client channel table.
amqscnxc YourQMName
And again with the wrong QM name â will fail
amqscnxc DUMMY
See how it could work or fail even if you supply the correct name for the QM on the connect call?
Peter Potkay
From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Paul Clarke
Sent: Monday, July 28, 2014 12:58 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT
Subject: Re: Attempting to use a Client channel definition table (CCDT)
Hi,
I would expect you to have to FTP the file in BIN mode. It is a binary file containing lots of nasty stuff which wouldnât appreciate being converted from EBCDIC to ASCII since they are not characters [Smile]
So, 2058 means that the client code could not find a definition of where to go for Queue Manager MQM9. This either means that it didnât find your CCDT, there is not CLNTCONN in the CCDT with a QMNAME value of MQM9 or (possibly) that you made a connection somewhere at it turned out not to be MQM9.
My guess is that the CCDT doesnât contain the CLNTCONN you are looking for. Perhaps the simplest thing is to download MO72 and have a quick look at the contents of your CCDT. Run MO72 with the ân flag and issue DIS CHL( * ) ALL and check that the channels are as you expected. If you really want to you can send it to me and Iâll use MQSCX and check that the format and content looks ok.
Cheers,
Paul.
Paul Clarke
www.mqgem.com<http://www.mqgem.com>
From: Livingston, Stuart J.<mailto:***@DTCC.COM>
Sent: Monday, July 28, 2014 5:51 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: Re: Attempting to use a Client channel definition table (CCDT)
Paul,
Just to let you know my knowledge level, up till now I never know that the client had an error log.
The error from AMQSGETC is:
[cid:***@01CFAA83.A0B66760]
MQCHLTAB= CDDT9.TAB
MQCHLLIB=C:\MQSeries
I deleted the previous version of AMQERR01.LOG, but after running AMQSGETC there was no log.
I re did my ftp to my PC sending the CCDT file in ASCII mode and I saw the following errors in the log
[cid:***@01CFAA83.A0B66760]
Even though the format of my table is incorrect (sent as ASCII) it appears that the utility is using my MQCHLLIB and MQCHLTAB variables,
After resending CCDT with BIN mode, and re-trying AMQSGETC, I still see the same results from the utility, but no additional errors in the MQ error log.
I am checking with other in my group who have successfully generated CCDT.
Respectfully,
Stu
Stuart J. Livingston
Lead Tech Systems Architect
Transaction and Messaging Technologies
DTCC New York
***@dtcc.com<mailto:***@dtcc.com>
212-855-8356
[cid:***@01CE0F88.44652010]
DTCC Confidential (Yellow)
From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Paul Clarke
Sent: Monday, July 28, 2014 10:48 AM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: Re: Attempting to use a Client channel definition table (CCDT)
Hi,
What did you set the MQCHLLIB and MQCHLTAB variables to ? And what was the exact response from AMQSGETC (including the error log),. Without this information itâs a little hard to know where you went wrong.
Cheers,
Paul.
Paul Clarke
www.mqgem.com<http://www.mqgem.com>
From: Livingston, Stuart J.<mailto:***@DTCC.COM>
Sent: Monday, July 28, 2014 3:36 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: Attempting to use a Client channel definition table (CCDT)
Hello,
I been assigned to a project that will require the use of a client channel definition table. Being that I have no experience with one, I figure that I will try to set one up to play with.
My plan is to generate a CCDT on Z/OS using the CSQUTIL utility and ftp it down to my windows work station.
Is it possible to use a CCDT from a Windows MQ client? If so how do I setup the MQ client to use my CCDT? Doing searches via google, I came across the variables MQCHLLIB and MQCHLTAB.
I have set these the variables and then used the sample program AMQSGETC to read messages on a mainframe queue manager, but the sample could not fine QMGR.
Does anyone have any suggestions?
Respectfully,
Stu
Stuart J. Livingston
Lead Tech Systems Architect
Transaction and Messaging Technologies
DTCC New York
***@dtcc.com<mailto:***@dtcc.com>
212-855-8356
[cid:***@01CE0F88.44652010]
DTCC Confidential (Yellow)
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************
To unsubscribe, write to ***@LISTSERV.MEDUNIWIEN.AC.AT and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html