| Author |
Message
|
| pezi |
 Posted: Mon Apr 28, 2008 6:51 am Post subject: Using AMQCLCHL.TAB created on Win QM for UNIX client |
 |
|
Novice
Joined: 08 Feb 2008
Posts: 15
Location: Vienna/Austria
|
Hi,
I have a MQServer (5.3) running on a Windows machine and created a client connection channel table file.
Now I tried to use this file instead the MQSERVER environment variable on a UNIX client because it permits to access multiple QueueManagers. Unfortunately this did not work out (reason code 2059).
When I was using the same file on Windows it was working.
Is there anything I have to consider when I am transferring the file to Unix (transferred it in binary mode using FTP)?
If this could not be transferred to another platform is there some kind of command line tool to create the AMQCLCHL.TAB file yourself on the operating system of your choice?
Best regards
Peter |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Apr 28, 2008 6:55 am Post subject: Re: Using AMQCLCHL.TAB created on Win QM for UNIX client |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pezi wrote: |
Is there anything I have to consider when I am transferring the file to Unix (transferred it in binary mode using FTP)?
|
Nope, that'll do it. Done it myself before now.
I would look into other possible causes of the 2059. There are a lot of them, and most have been discussed on the forum. Many have nothing to do with code or WMQ configuration.
There's nothing to stop you (to eliminate doubt) creating another file on Unix and trying to connect with that (having first renamed the original file - remember that's only the default name) but I'd be very surprised if that was the root cause.
Check also that the TAB file is in the right place on the Unix box, has the right file permissions, right environment variables in the right scope, etc, etc. It's easy to overlook the obvious. I've done that as well before now. 
Also consider moving to v6. WMQ v5.3 is out of support.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| anderc1 |
| Posted: Mon Apr 28, 2008 11:31 am Post subject: |
|
|
Acolyte
Joined: 11 Sep 2002
Posts: 55
Location: Research Triangle Park, NC
|
| Did you create the svrconn channel on the Windows box? Check the clients manual. The svrconn channel and the client channel will have the same name. Sounds weird but that's how it works. |
|
| Back to top |
|
|
| pezi |
| Posted: Tue Apr 29, 2008 12:28 am Post subject: |
|
|
Novice
Joined: 08 Feb 2008
Posts: 15
Location: Vienna/Austria
|
Hi,
Thank you for your hints. I got it working. The reason was that in the connection name I was referring to a computer name which was not known in the Unix system. After changing it to an IP-Address it worked.
Nevertheless I would like to know how to build such a table on Unix. In Windows I used the MQ Explorer.
best regards
Peter |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 29, 2008 12:39 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| pezi wrote: |
| Nevertheless I would like to know how to build such a table on Unix. |
Check out the Clients manual for full details, and the Command Reference for syntax & parameter details.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Apr 29, 2008 12:47 pm Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
You can also use MO72:
export MQCHLLIB=.
mqsc -n
<define your client channels>
END
But read the documentation anyway... |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Apr 30, 2008 3:48 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
MQ Reason Code 2059 covers a multitude of sins. It always writes useful diagnostic messages to the tail of <mqinstalldir>/errors/AMQERR01.LOG.
You should always check there first, and copy/paste the error message to this forum if the message does not make sense.
CCDT files are in platform independent format. They can be created on any distributed or z/OS platform and used on any other supported platform.
CCDT files are not backward compatible across MQ versions (except MQ 5.1 <-> 5.2). ie. CLNTCONN channel definitions in a file created or altered on V6.0 will not work on V5.3. SupportPac MO72 can come to the rescue so that you don't need a old MQ Server system to manage CCDT files for back-level MQ Client-only systems.
_________________
Glenn |
|
| Back to top |
|
|
|
|
