Author |
Message
|
sunshine |
Posted: Wed Dec 17, 2008 8:48 pm Post subject: QueueManager not getting added to the cluster |
|
|
Novice
Joined: 07 Dec 2008 Posts: 13
|
I am trying to introduce a new Qmgr in a cluster. I have defined the chhanel already like wise with cluster names.But "dis clusqmgr(*)"--this command gives the output like....
This is for CLUSSDR Channel
--------------------------------------
CLUSQMGR(SYSTEM.TEMPQMGR.mqrepot1.intra.aexp.com(10004))
CHANNEL(NSFMCCLT01.PTPRET11) CLUSTER(NSFMCCLT01)
This is for CLUSRCVR Channel
-------------------------------------
AMQ8441: Display Cluster Queue Manager details.
CLUSQMGR(WPLIU616d) CHANNEL(NSFMCCLT01.WPLIU616D) CLUSTER(NSFMCCLT01)
For CLUSRCVR Channels the credentials are coming properly but for CLUSSD Channels there are some mistakes. I have already checked the conname parameter of these channels..conname is perfect.Still it is not able to identify the repository..What to do ?
For Information I have already checked conname parameter and tried to recreate the channels again,but the problem remains same. I refreshed the cluster also.
Generally why this kind of problem arises please let me know.
Thanks in Advance |
|
Back to top |
|
 |
zhanghz |
Posted: Wed Dec 17, 2008 10:07 pm Post subject: |
|
|
Disciple
Joined: 17 Jun 2008 Posts: 186
|
this new qmgr is a PR qmgr? list your definitions of your CLUSSDR & CLUSRCVR in this new qmgr, and definition of your CLUSRCVR in your FR qmgr (i assume it is mqrepot1.intra.aexp.com) that this new qmgr connects to. |
|
Back to top |
|
 |
sunshine |
Posted: Wed Dec 17, 2008 10:40 pm Post subject: |
|
|
Novice
Joined: 07 Dec 2008 Posts: 13
|
can you be little more elucidative. Cause I did nt get the thought and FR and PR---are u indicate the repositories ?
Please let me know in details--what are you asking cause this will help in solving the problem. |
|
Back to top |
|
 |
zhanghz |
Posted: Wed Dec 17, 2008 10:48 pm Post subject: |
|
|
Disciple
Joined: 17 Jun 2008 Posts: 186
|
thought you would be able to guess the meanings.
PR: partial repository
FR: full repository |
|
Back to top |
|
 |
Mr Butcher |
Posted: Wed Dec 17, 2008 11:31 pm Post subject: |
|
|
 Padawan
Joined: 23 May 2005 Posts: 1716
|
Looks like you have a problem to connect to the FR Queudemanager, thats why you see that SYSTEM.TEMPQMGR name instead of the "real" name.
Check the channel NSFMCCLT01.PTPRET11, i assume it is not "running". Solve that channel issue, and if your definitions are correct then you should be fine. _________________ Regards, Butcher |
|
Back to top |
|
 |
sunshine |
Posted: Thu Dec 18, 2008 1:05 am Post subject: |
|
|
Novice
Joined: 07 Dec 2008 Posts: 13
|
The channels were not running.Channels are getting stopeed automatically.
After starting the channel also the situation is still the same  |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Dec 18, 2008 1:13 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
sunshine wrote: |
The channels were not running.Channels are getting stopeed automatically.
After starting the channel also the situation is still the same  |
Channels do not get stopped automatically. They stop for a reason and they are probably in retry status. Check the qmgr's error logs on both sides. It should contain something about why the channels are not communicating.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
sunshine |
Posted: Thu Dec 18, 2008 3:36 am Post subject: |
|
|
Novice
Joined: 07 Dec 2008 Posts: 13
|
Surprisingly nothing is there in the error log--No entry with todays date.... |
|
Back to top |
|
 |
Vitor |
Posted: Thu Dec 18, 2008 3:43 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
sunshine wrote: |
Surprisingly nothing is there in the error log--No entry with todays date.... |
So the channel is in a STOPPED status. You start it, and it "automatically" goes back into STOPPED. With no error log to indicate why.
If this is indeed the case, you need to raise a PMR with IBM. A channel in STOPPED status has either been manually placed in that status or has stopped in response to an error. Both of these events should be (and typically are) logged. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Mr Butcher |
Posted: Thu Dec 18, 2008 6:41 am Post subject: |
|
|
 Padawan
Joined: 23 May 2005 Posts: 1716
|
at what error log do you look? _________________ Regards, Butcher |
|
Back to top |
|
 |
|