| Author |
Message
|
| shashivarungupta |
 Posted: Sun Nov 21, 2010 10:41 am Post subject: AMQCLCHL.TAB |
 |
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
Hi Guys,
Whenever we create a client connection channel , its definition and authentication info. goes into a binary file AMQCLCHL.TAB automatically (not considering z/OS here).
Now, as I have 10 applications they want to connect to the server queue manager using 'its' .TAB file.
Whenever we create a Client conn. channel , its definition and authentication info. goes to the 'default' AMQCLCHL.TAB file, which also contains the definition of the system default client conn channel. {deletion of this file is not at all recommended & editing is not possible.}
Now, applications 1,2,3 wants a *.tab files say client1.TAB, client2.TAB, client3.TAB which would have client conn. definitions , How can I create individual .TAB files for each of'em, when definitions of those gets appended under AMQCLCHL.TAB file ?
I want to give them their .tab file which would contain the definition of only its client conn. channel.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sun Nov 21, 2010 12:09 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| How can I create individual .TAB files for each of'em, when definitions of those gets appended under AMQCLCHL.TAB file ? |
Many shops create a qmgr for the sole purpose of defining (updating) CLNTCONN definitions (the .TAB file). This qmgr (or these qmgrs) do no application or message processing.
Once the new/updated .TAB file is created, rename it to whatever you want; and make it available to the appropriate client platforms. I'd suggest a filename that includes version and/or date-time - some meaningful name.
_________________
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 |
|
|
| exerk |
| Posted: Sun Nov 21, 2010 12:16 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
1. Copy the AMQCLCHL.TAB file to a location of your choice, to use as a template;
2. Make a copy of the above file and use the MO72 SupportPac to define the CLNTCONN within the copy;
3. Rinse-and-repeat the process for as many clients as necessary.
Just one method, undoubtedly there are others...
_________________
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 |
|
|
| shashivarungupta |
| Posted: Sun Nov 21, 2010 12:19 pm Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| Quote: |
| Once the new/updated .TAB file is created, rename it to whatever you want; and make it available to the appropriate client platforms. I'd suggest a filename that includes version and/or date-time - some meaningful name. |
That I did.
Tomorrow, suppose I have to alter some properties of client conn channel then I would have to rename client1.TAB to AMQCLCHL.TAB FILE so that MQ will find the file with 'default name AMQCLCHL.TAB' and will update it accordingly. After the update would be done, I would go back & rename the updated file to client.TAB. Correct ?
And I believe alter (say mcauser) on server conn ( to which client conn was pointing to ) won't affect the client.TAB file. Correct ?
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Nov 21, 2010 1:52 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I would have to rename client1.TAB to AMQCLCHL.TAB |
Nope. Each time you define/alter/delete a CLNTCONN channel definition, a new instance of AMQCLCHL.TAB is created.
I'm presuming that you want to have a unique client channel table for each individual client platform.
If so, do this:
1) create a client1.def file that contains the CLNTCONN definitions for client1 platform.
2) runmqsc qmgrname <client1.def
3) AMQCLCHL.TAB is now the client table for client1
4) rename AMQCLCHL.TAB to client1.tab (or client1.TAB)
Repeat this for each individual client.
_________________
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 |
|
|
| gbaddeley |
| Posted: Sun Nov 21, 2010 4:13 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
A method I use is to copy a known empty tab file to the tab file I want to build (eg. myapp1.tab), and then start the qmgr with the MQCHLLIB and MQCHLTAB environment variables set to point to the file. Subsequent DEFINE CHANNEL(xxx) CHLTYPE(cltnconn) will then create channels in that file.
HTH,
_________________
Glenn |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Nov 21, 2010 4:34 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
As you can see, there are a variety of ways to accomplish this task.
Pick a method, document it well, then stick with it.
I've become very fond of renaming the .tab file to include date/time/version info to identify which .tab goes with which client. C011110.TAB would mean client 01, 1110 would mean November 2010.
An alternative is to merely give the .tab file a filename with a sequence number (T00001.TAB, T00002.TAB; and keep track of (document) which .tab goes with which client.
_________________
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 |
|
|
| zpat |
| Posted: Sun Nov 21, 2010 11:09 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
It's all a lot easier to keep a text file as the TAB source and use MO72 to re-create it each time you need to change/add/delete anything.
Also M072 can set the MQ product version of the file, because it's not downward compatible so this should be set at the lowest version needed (unless you need new features). |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Mon Nov 22, 2010 3:50 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| Quote: |
| Each time you define/alter/delete a CLNTCONN channel definition, a new instance of AMQCLCHL.TAB is created. |
If thats not happening as it should, then what could be the reasons for that ?
And when we delete the client conn. channel, we do that by mentioning the following command
DELETE CHANNEL( channel_name ) CHLTABLE(CLNTTBL)
and isn't it MQ would search the definition of client conn. channel in default 'AMQCLCHL.TAB' file, obviously instead of customized Client1.TAB file.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Mon Nov 22, 2010 5:01 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| exerk wrote: |
1. Copy the AMQCLCHL.TAB file to a location of your choice, to use as a template;
2. Make a copy of the above file and use the MO72 SupportPac to define the CLNTCONN within the copy;
3. Rinse-and-repeat the process for as many clients as necessary.
|
This is one of the Good Methods to follow.
(I have tried it on windows for now and will do it on aix aswell.) 
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Nov 22, 2010 5:16 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| shashivarungupta wrote: |
| exerk wrote: |
1. Copy the AMQCLCHL.TAB file to a location of your choice, to use as a template;
2. Make a copy of the above file and use the MO72 SupportPac to define the CLNTCONN within the copy;
3. Rinse-and-repeat the process for as many clients as necessary.
|
This is one of the Good Methods to follow.
(I have tried it on windows for now and will do it on aix as well.) |
Why? Why not concentrate your TAB file management to one place/platform and distribute as required?
_________________
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 |
|
|
| bruce2359 |
| Posted: Mon Nov 22, 2010 6:50 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The .TAB file is platform-neutral - you can create a .TAB on Windoze, and use it on AIX, for example.
_________________
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 |
|
|
| shashivarungupta |
| Posted: Mon Nov 22, 2010 8:54 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| exerk wrote: |
| shashivarungupta wrote: |
| exerk wrote: |
1. Copy the AMQCLCHL.TAB file to a location of your choice, to use as a template;
2. Make a copy of the above file and use the MO72 SupportPac to define the CLNTCONN within the copy;
3. Rinse-and-repeat the process for as many clients as necessary.
|
This is one of the Good Methods to follow.
(I have tried it on windows for now and will do it on aix as well.) |
Why? Why not concentrate your TAB file management to one place/platform and distribute as required? |
I never used MO72 to create .TAB File so I 'tried' on dummy qmgr on windows on which MO72 pack was lying.
Now I can use the same method over actual qmgr on AIX server where still I have to place MO72 pack somewhere. Thats why ! 
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Nov 22, 2010 8:58 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| shashivarungupta wrote: |
| exerk wrote: |
| Why? Why not concentrate your TAB file management to one place/platform and distribute as required? |
I never used MO72 to create .TAB File so I 'tried' on dummy qmgr on windows on which MO72 pack was lying.
Now I can use the same method over actual qmgr on AIX server where still I have to place MO72 pack somewhere. Thats why ! |
Please re-read bruce2359's post, very carefully...
_________________
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 |
|
|
| shashivarungupta |
| Posted: Mon Nov 22, 2010 8:58 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| bruce2359 wrote: |
| The .TAB file is platform-neutral - you can create a .TAB on Windoze, and use it on AIX, for example. |
Ya.. and by this standard, I would create .TAB Files for diff. appls. which are suppose to connect to AIX Qmgr.
Very Good Infor. indeed. thanks Bruce.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
|
|
