Author |
Message
|
sebastia |
Posted: Fri Sep 28, 2007 1:37 pm Post subject: tool to display AMQCLCHL.TAB contents |
|
|
 Grand Master
Joined: 07 Oct 2004 Posts: 1003
|
We are having some problems with the way our MQ clients connect to the MQ Servers using the AMQCLCHL.TAB (different) tables.
So, we would like to verify that the (different) tables we are generating have the contents they are supposed to have.
>>> Is there any (easy to manage) tool to display the contents
of a given "*.TAB" AMQCLCHL.TAB-like table ?
Thanks. Sebastian. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Sep 28, 2007 8:18 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Generally the channel table is copied from a specific qmgr. So you need to connect to the qmgr and examine the source.
runmqsc or MQExplorer can show you the content of the qmgr's channel table.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
sebastia |
Posted: Sat Sep 29, 2007 1:32 am Post subject: |
|
|
 Grand Master
Joined: 07 Oct 2004 Posts: 1003
|
Thanks, mr Saper
I have been told to issue
"runmqsc command "dis chl(*) chltype(clntconn) all"
But this is still in the MQ Server
and the "real truth" is the table that we do have in the MQ Client
So, to see the "real data", everybody is looking for the tool
to have a look inside the table available NOW and HERE.
I mean - the source maybe is gone or re-configured or confused or ...
I am sure you understand ...
Thanks for your sugestion(s) - lots of them, I know. |
|
Back to top |
|
 |
jefflowrey |
Posted: Sat Sep 29, 2007 5:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
M071 is supposed to have some capabilities for this.
I don't use it, because I always have to spend time trying to figure out how it wants things done.
But I've heard mention that it can read and manipulate client channel tables. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
sebastia |
Posted: Sat Sep 29, 2007 6:05 am Post subject: |
|
|
 Grand Master
Joined: 07 Oct 2004 Posts: 1003
|
|
Back to top |
|
 |
jefflowrey |
Posted: Sat Sep 29, 2007 7:03 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I don't use MO72 either. It's entirely possible that I got them confused. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Sat Sep 29, 2007 8:17 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Its MO72.
And although the channel tables are binary if you open them in VIEW ONLY mode you can usually see the hostnames and channel names in plain text, giving you a clue as to what QMs this table points to. Don't attempt to directly edit the channel table file! _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
sebastia |
Posted: Sat Sep 29, 2007 10:31 am Post subject: |
|
|
 Grand Master
Joined: 07 Oct 2004 Posts: 1003
|
ok, Peter - I was doing some basic "TYPE TABLE_1.TAB" command
and saw its "string" contents.
( by the way - Mark Russinovich has an excelent "strings" command in www.sysinternals.com )
But the biggest problem is that one DOS session sets MQCHLLIB / TAB
and those values make the table creation write the table
in "unexpected" places ...
>>> http://www-1.ibm.com/support/docview.wss?uid=swg21173095
Now all looks under control, except that this process is VERY MANUAL
I mean : we shall have thousands of MQ Clients,
and 6 MQ Servers, so we shall create 6 tables,
for 6 groups of clients to be created.
I supose the naming convention of the channels included in a AMQCLCHL.TAB table is important, as it CAN BE DISPLAYED using the "TYPE AMQCLCHL.TAB" command ....
That is my experience until now ...
And the important conclusion (I did a quite an serious test ) :
"In that table it will try connecting
>>> alphabetically <<<
by channel name assuming the channels and MQCONN call have a blank QM name specified"
Thanks to all of you involved. You did help me do my job (properly).
Sebastian. |
|
Back to top |
|
 |
belchman |
Posted: Mon Oct 01, 2007 10:18 am Post subject: |
|
|
Partisan
Joined: 31 Mar 2006 Posts: 386 Location: Ohio, USA
|
The way I do it is to copy the AMQCLCHL.TAB to /var/mqm/qmgrs/TestQMgrName/@ipcc. Then I can look at the clientconns on the qmgr that are loaded from the AMQCLCHL.TAB. _________________ Make three correct guesses consecutively and you will establish a reputation as an expert. ~ Laurence J. Peter |
|
Back to top |
|
 |
sebastia |
Posted: Mon Oct 01, 2007 10:27 am Post subject: |
|
|
 Grand Master
Joined: 07 Oct 2004 Posts: 1003
|
You mean you have a dedicated queue manager only to be able a "runmqsc" against it and see its CLNTCONN ?
I think it is a great idea ! |
|
Back to top |
|
 |
belchman |
Posted: Mon Oct 01, 2007 10:33 am Post subject: |
|
|
Partisan
Joined: 31 Mar 2006 Posts: 386 Location: Ohio, USA
|
Any queue manager will work. I actually use explorer to look at client conns, but runmqsc will work.
The important thing to remember is that the clientconns (I believe I am correct here but u mite want to verify) on a queuemgr are used for nothing except to create the client channel table. The clients actually use the svrconns that the client channel table entries correspond to. _________________ Make three correct guesses consecutively and you will establish a reputation as an expert. ~ Laurence J. Peter |
|
Back to top |
|
 |
sebastia |
Posted: Mon Oct 01, 2007 10:42 am Post subject: |
|
|
 Grand Master
Joined: 07 Oct 2004 Posts: 1003
|
Yes, I agree and you are 100 % right.
The CLNTCONN lines in a script are only to create the table,
and all of then have to have a corresponding SVRCONN definition,
that is the only that "realy" exists. |
|
Back to top |
|
 |
bruce2359 |
Posted: Mon Oct 01, 2007 1:41 pm Post subject: |
|
|
Guest
|
An option: Designate one qmgr to be the one that generates the client channel table for all clients and all other qmgrs. |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Oct 01, 2007 1:47 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Hey, I've got a great idea.
Why not set up a single queue manager, that's only used for managing client channel tables? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
bruce2359 |
Posted: Mon Oct 01, 2007 2:28 pm Post subject: |
|
|
Guest
|
Oh, Jeff.  |
|
Back to top |
|
 |
|