| Author |
Message
|
| TonyD |
 Posted: Mon Dec 15, 2008 12:59 pm Post subject: Removing an obsolete FR QMID |
 |
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
I had to recreate a Linux FR queue manager (unreadable queue). This worked OK and the queue manager is back in the repository as a FR with a new QMID.
However a mainframe PR queue manager shows two QMIDs for that FR queue manager, the old deleted one and the new one, and currently does not seem to be communicating at all with the new FR.
I tried a 'reset cluster(xxx) qmid(oldFR_QMID)' at the new FR queue manager in an attempt to remove the reference from the PR but no message was even sent.
Is the best approach now to simply remove the PR queue manager from the cluster and then add it back in to the cluster? |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Mon Dec 15, 2008 2:21 pm Post subject: Re: Removing an obsolete FR QMID |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| TonyD wrote: |
I tried a 'reset cluster(xxx) qmid(oldFR_QMID)' at the new FR queue manager in an attempt to remove the reference from the PR but no message was even sent.
|
Maybe the new FR is not in the cluster properly yet?
How about trying the RESET to eject the old FR from the 2nd FR that has been up and stable throughout?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| TonyD |
| Posted: Mon Dec 15, 2008 4:00 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
Thanks Peter, the new FR was communicating OK with the other queue managers in the cluster and appeared to have joined the cluster correctly.
In the end I issued 'REFRESH CLUSTER (xxx) REPOS(YES)' at the PR that was confused and this appeared to sort everything out satisfactorily. |
|
| Back to top |
|
|
| zhanghz |
| Posted: Mon Dec 15, 2008 4:31 pm Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
| I encountered the same thing 3 times. Frustrating, PR channels kept on retrying to connect to another QMID (whose IP is a DR server's IP, which is the strange part). Still don't know what caused that.. |
|
| Back to top |
|
|
| firoj.badsa |
| Posted: Wed Dec 17, 2008 4:58 am Post subject: |
|
|
Centurion
Joined: 16 Feb 2007
Posts: 104
|
Old queuemanager was not deleted properly. Login to FR and issue command
RESET CLUSTER(CLUSTERNAME) QMID('QMID FOR OLD QMANAGER') ACTION(FORCEREMOVE) QUEUES(YES) |
|
| Back to top |
|
|
| TonyD |
| Posted: Wed Dec 17, 2008 11:43 am Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
| firoj.badsa wrote: |
Old queuemanager was not deleted properly. Login to FR and issue command
RESET CLUSTER(CLUSTERNAME) QMID('QMID FOR OLD QMANAGER') ACTION(FORCEREMOVE) QUEUES(YES) |
That was the first thing I tried ... no messages passed to the PR and the old QMID remained there. |
|
| Back to top |
|
|
| zhanghz |
| Posted: Wed Dec 17, 2008 10:14 pm Post subject: |
|
|
Disciple
Joined: 17 Jun 2008
Posts: 186
|
| in my case last time (last 3 times), the FR QMGRs didn't have the old qmid in their repositories. Only thing I could do was to refresh cluster repos(yes) on the PR QMGR. |
|
| Back to top |
|
|
|
|
