Author |
Message
|
zaklum |
Posted: Mon Aug 29, 2005 10:37 am Post subject: Problem when deleting cluster channel |
|
|
Voyager
Joined: 17 Mar 2005 Posts: 96 Location: Boca Raton
|
When trying to delete a cluster channel I get a "channel not found" error even though the channel exist:
dis chs(*)
3 : dis chs(*)
AMQ8417: Display Channel Status details.
CHANNEL(TO.CHANNEL1.TCP) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE)
CONNAME(127.0.0.1) CURRENT
CHLTYPE(CLUSSDR) STATUS(STOPPED)
RQMNAME()
DELETE CHANNEL(TO.CHANNEL1.TCP)
5 : DELETE CHANNEL(TO.CHANNEL1.TCP)
AMQ8227: Channel TO.CHANNEL1.TCP not found. |
|
Back to top |
|
 |
vennela |
Posted: Mon Aug 29, 2005 10:47 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
That might be an auto-defined channel. |
|
Back to top |
|
 |
wschutz |
Posted: Mon Aug 29, 2005 11:05 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
Quote: |
That might be an auto-defined channel. |
You can tell by:
Code: |
runmqsc your-qmgr
dis clusqmgr(*) channel(TO.CHANNEL1.TCP) deftype
|
If its a CLUSSDRA, then it was auto-defined. _________________ -wayne |
|
Back to top |
|
 |
zaklum |
Posted: Tue Aug 30, 2005 10:30 am Post subject: |
|
|
Voyager
Joined: 17 Mar 2005 Posts: 96 Location: Boca Raton
|
No, this is not a system generated channel.
This channel was created by a developer from his local machine. |
|
Back to top |
|
 |
wschutz |
Posted: Tue Aug 30, 2005 10:35 am Post subject: |
|
|
 Jedi Knight
Joined: 02 Jun 2005 Posts: 3316 Location: IBM (retired)
|
so the output from the display is CLUSSDR? _________________ -wayne |
|
Back to top |
|
 |
Carla Viragh |
Posted: Tue Feb 20, 2007 5:28 am Post subject: |
|
|
 Voyager
Joined: 31 Oct 2003 Posts: 92 Location: São Paulo - Brasil
|
Hello!
I have exactly the same problem! A STOPPED status channel (CLUSSDRA) that should disappear because the destination queue manager doesn't exist anymore (neither the channel itself).
If I try to find the channel: dis chl(channel.name), MQ says "channel not found".
If I try to find the status: dis chs(channel.name), MQ says "channel is stopped".
It's bad because Tivoli shows this as a problem. We created a rule to ignore this channel, but... not the best solution.
Additional information: This and the destination queue managers were full repositories but others were elected to be FR. After changes, this channel that was a CLUSSDRB when was excluded became a CLUSSDRA at the same time like expected. But now, the destination queue manager doesn't exist, so I suppose the channel should vanish. Well, it vanished but not its status…
 _________________ Carla Viragh |
|
Back to top |
|
 |
|