| Author |
Message
|
| MQ_Lover |
 Posted: Wed Nov 06, 2013 6:47 am Post subject: MQ Cluster auto defined channels |
 |
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
Hi Experts,
I have a issue whereby I have added a Queue Manger on Windows to a MQ cluster whose full Repositories are Mainframe Queue Managers, the issue is the Windows server is in DMZ layer and hence cannot resolve DNS but before I knew that I added the Windows Queue Manager to cluster and it failed then I changed the DNS to be IP for one of the full repositories and it got added fine but for the remaining two full repositories the cluster auto-defined the clussdr channels got DNS populated and they are in RETRYING state as these channels got auto defined I cannot alter them hence decided to removed the Queue Manager from Cluster and the reference to one of the full repository is cleaned but the other two Queue Managers still have the clussdr channel from Windows to these two in retrying state. I need your advise how could I get rid of this as on Windows Queue Manager it is continously writing in error logs as below. I have ***** the server details as cannot disclose.
Any help appreciated.
I have a done a refresh cluster repos(no) - do I need to do repos(yes) ?
-------------------------------------------------------------------------------
06/11/2013 14:35:57 - Process(9268.54410) User(MUSR_MQADMIN) Program(amqrmppa.exe)
Host(********)
AMQ9205: The host name supplied is not valid.
EXPLANATION:
The supplied TCP/IP host name '****.SYSTEMS.UK.****' could not be resolved into
a network address. Either the name server does not contain the host, or the
name server was not available.
ACTION:
Check the TCP/IP configuration on your host. |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Nov 06, 2013 6:56 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
1. How many FRs do you have, because your post implies you have more than two?
2. The Info Centre details how to clean up 'broken' clusters, and the Info Centre should be your first port of call;
3. If there are issues crossing DMZ boundaries, e.g. DNS resolution, then MQ Internet Pass Thru (SupportPac MS81) is your friend here.
_________________
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 |
|
|
| MQ_Lover |
| Posted: Wed Nov 06, 2013 7:13 am Post subject: |
|
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
| Thanks Exerk - We have 3 Full Repositories. I would check that do you have exact link please for brokern cluster one, can't use MQInternet Passthru as not allowed as per company policies |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 06, 2013 7:19 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| MQ_Lover wrote: |
| We have 3 Full Repositories. |
Don't unless you have a really, really good reason. This has been the subject of much debate in here and you should review these discussions to see if you have a really, really good reason or just a management requirement for 3 because it sounds a nice number.
| MQ_Lover wrote: |
| I would check that do you have exact link please for brokern cluster one, |
The InfoCenter has a search facility which gave me this as the first hit.
| MQ_Lover wrote: |
| can't use MQInternet Passthru as not allowed as per company policies |
What policy does it violate? I don't believe you have a policy "The MQ Internet Pass Thru (MS81) is never to be used" unless the author of that support pac owes your CIO money.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| MQ_Lover |
| Posted: Wed Nov 06, 2013 9:29 am Post subject: |
|
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
Hi Vitor - thanks for the link and details
| Quote: |
| Don't unless you have a really, really good reason. This has been the subject of much debate in here and you should review these discussions to see if you have a really, really good reason or just a management requirement for 3 because it sounds a nice number |
This is a 10 year old Cluster and hence I cannot change it, it's out of my hand big companies have as you said correctly for a number these kind of setup
I checked the Troubleshotting link and not much help as understandibly the issue is conname having DNS in the auto-defined CLUSSDR definition changing the equivalent CLUSRCVR conname to have IP would be a fix but I won't be able to do that and change the CONNAME for the CLUSRCVR on other full repositories, I just need to find a way to get this broken Windows Queue Manager out of the cluster cleanly and stop filling error logs - is their anyway around without touching the other full repositores please |
|
| Back to top |
|
|
| MQ_Lover |
| Posted: Thu Nov 07, 2013 8:06 am Post subject: |
|
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
| Hi - Anyone, any suggestions ? |
|
| Back to top |
|
|
| rammer |
| Posted: Thu Nov 07, 2013 8:28 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
| If you have removed the Windows QMGR out of the Cluster, but the REPOS can still see it hanging around you could just log onto each REPOS and issue RESET CLUSTER(CLUS NAME) ACTION( FORCEREMOVE ) QMNAME( string ) | QMID( string ) |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 07, 2013 9:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| rammer wrote: |
| If you have removed the Windows QMGR out of the Cluster, but the REPOS can still see it hanging around you could just log onto each REPOS and issue RESET CLUSTER(CLUS NAME) ACTION( FORCEREMOVE ) QMNAME( string ) | QMID( string ) |
But you'll be much better off over all unsharing all objects from the cluster and dismantling it in proper order and then creating it again properly.
Once you've shot yourself in the foot, you should try to avoid switching to larger caliber weaponry and firing again. |
|
| Back to top |
|
|
| MQ_Lover |
| Posted: Thu Nov 07, 2013 9:21 am Post subject: |
|
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
Hi Rammer,
Thanks for that - but does this reset command safe for other members of the cluster and won't affect channels to other queue managers as this is a huge cluster having around 256 Queue Managers.
Regards,
Vishal |
|
| Back to top |
|
|
| MQ_Lover |
| Posted: Thu Nov 07, 2013 9:23 am Post subject: |
|
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
| Hi mqjeff - I can't dismantle this cluster it's gigantic, all I could do in this cluster is basically with regards to this corrupt windows queue manager only |
|
| Back to top |
|
|
| rammer |
| Posted: Thu Nov 07, 2013 10:33 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
| MQ_Lover wrote: |
Hi Rammer,
Thanks for that - but does this reset command safe for other members of the cluster and won't affect channels to other queue managers as this is a huge cluster having around 256 Queue Managers.
Regards,
Vishal |
Here you go, this probably describes how your cluster is currently.
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=%2Fcom.ibm.mq.csqzah.doc%2Fqc11460_.htm
When you do the force you are telling it a specific Queue Manager Name or a QMID. You can get the QMID from the Repos by issuing dis clusqmgr(QMGNAME) QMID |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 07, 2013 11:33 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Not sure but I thought it crept back into the FR if there is somewhere in the cluster some msgs on a SCTQ or NamedCTQ that are slotted for this qmgr. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| MQ_Lover |
| Posted: Fri Nov 08, 2013 3:09 am Post subject: |
|
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
Hi fjb_saper -there are messages on SYSTEM.CLUSTER.TRANSMIT.QUEUE looks like for each full Repository Queue Manager it is still linked to as below
58 51 48 20 01 00 00 00--53 59 53 54 45 4D 2E 43 |XQH ....SYSTEM.C|
00010 4C 55 53 54 45 52 2E 43--4F 4D 4D 41 4E 44 2E 51 |LUSTER.COMMAND.Q|00020 55 45 55 45 20 20 20 20--20 20 20 20 20 20 20 20 |UEUE |
00030 20 20 20 20 20 20 20 20--4D 42 32 35 20 20 20 20 | MB25 |
00040 20 20 20 20 20 20 20 20--20 20 20 20 20 20 20 20 | |
00050 20 20 20 20 20 20 20 20--20 20 20 20 20 20 20 20 | |
00060 20 20 20 20 20 20 20 20--4D 44 20 20 01 00 00 00 | MD ....|
00070 00 00 00 00 08 00 00 00--4F 5D 2F 01 00 00 00 00 |........O]/.....|
00080 22 02 00 00 52 03 00 00--4D 51 41 44 4D 49 4E 20 |"...R...MQADMIN |
00090 00 00 00 00 01 00 00 00--41 4D 51 20 43 4E 57 33 |........AMQ CNW3|
000A0 35 31 35 47 46 53 20 20--57 21 2F 52 20 00 07 26 |515GFS W!/R ..&|
000B0 00 00 00 00 00 00 00 00--00 00 00 00 00 00 00 00 |................|
000C0 00 00 00 00 00 00 00 00--00 00 00 00 20 20 20 20 |............ |
000D0 20 20 20 20 20 20 20 20--20 20 20 20 20 20 20 20 | |
000E0 20 20 20 20 20 20 20 20--20 20 20 20 20 20 20 20 | |
000F0 20 20 20 20 20 20 20 20--20 20 20 20 43 4E 57 33 | CNW3|
00100 35 31 35 47 46 53 20 20--20 20 20 20 20 20 20 20 |515GFS |
00110 20 20 20 20 20 20 20 20--20 20 20 20 20 20 20 20 | |
00120 20 20 20 20 20 20 20 20--20 20 20 20 4D 55 53 52 | MUSR|
00130 5F 4D 51 41 44 4D 49 4E--16 01 05 15 00 00 00 B9 |_MQADMIN.......╣|
00140 94 4E AB 4D 6C FC E8 2D--C1 02 5C F4 03 00 00 00 |öN½Ml³Þ-┴.\¶....|
00150 00 00 00 00 00 00 00 0B--20 20 20 20 20 20 20 20 |....... |
00160 20 20 20 20 20 20 20 20--20 20 20 20 20 20 20 20 | |
00170 20 20 20 20 20 20 20 20--07 00 00 00 65 62 53 70 | ....ebSp|
00180 68 65 72 65 20 4D 51 5C--62 69 6E 5C 61 6D 71 72 |here MQ\bin\amqr|
Also the SYSTEM.CLUSTER.HISTORY.QUEUE and SYSTEM.CLUSTER.REPOSITORY.QUEUE has messages all are for relating to these two full repository only. |
|
| Back to top |
|
|
| rammer |
| Posted: Fri Nov 08, 2013 3:13 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
I have recently (on numerous occasions) had to run the RESET command and everything has been fine.
I have to admit I didnt check the SCTQ, but in terms of History Queue that would not be a worry. |
|
| Back to top |
|
|
| MQ_Lover |
| Posted: Fri Nov 08, 2013 3:22 am Post subject: |
|
|
Acolyte
Joined: 15 Jul 2013
Posts: 67
|
Hi Rammer - Thanks for the link and it does looks like this is what I wanted, we are definitely in a condition of a broken cluster and these auto-defined cluster channels were the issue, this details that the last resort is to force remove the Queue Manager from the cluster as the doc reads -
| Quote: |
| Using the RESET CLUSTER command is the only way to delete auto-defined cluster-sender channels. You are unlikely to need this command in normal circumstances. The IBM® Support Center might advise you to issue the command to tidy up the cluster information held by cluster queue managers. Do not use this command as a short cut to removing a queue manager from a cluster. The correct way to remove a queue manager from a cluster is described in |
I am going to use this now to remove the Queue Manager from the two full repositories - Many thanks for this GOLDEN command |
|
| Back to top |
|
|
|
|
