| Author |
Message
|
| techno |
 Posted: Wed Feb 11, 2004 11:23 am Post subject: Remote administration |
 |
|
Chevalier
Joined: 22 Jan 2003
Posts: 429
|
when I do
runmqsc -w 30 targetqmgr
I am getting error 'AMQ8146: WebSphere MQ queue manager not available', even though I defined all the channels/xmitq, started command servers and listeners
Am I missing anything? Advise pls.
Thanks |
|
| Back to top |
|
 |
| TCV |
| Posted: Wed Feb 11, 2004 12:09 pm Post subject: hi |
|
|
Apprentice
Joined: 21 Aug 2003
Posts: 48
|
AMQ8146 says the QueueManager is not running.Make sure the QM is running.
Thanks
TC Venkatesan |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed Feb 11, 2004 12:57 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
|
| Back to top |
|
|
| techno |
| Posted: Wed Feb 11, 2004 8:49 pm Post subject: |
|
|
Chevalier
Joined: 22 Jan 2003
Posts: 429
|
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Thu Feb 12, 2004 7:48 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
This may sound stupid but check to make sure the path you created between your queue managers actually gets you to the "targetqmgr".
After you defined the channels, did you issue the "START CHL()" command?
Also, how many QMgr hopes will the message be doing? (i.e. A -> B-> C -> D) Are all the components (command server, listener, QMgrs, etc...) running?
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| Balmer |
| Posted: Thu Feb 12, 2004 8:16 am Post subject: |
|
|
Novice
Joined: 19 Jun 2003
Posts: 13
|
hi,
make sure that ur local queue manager is the default queue manager... |
|
| Back to top |
|
|
| leongor |
| Posted: Thu Feb 12, 2004 10:35 am Post subject: |
|
|
Master
Joined: 13 May 2002
Posts: 264
Location: Israel
|
Have you defined xmitQ to remote queue manager with the exactly same name ? ( must be equal, including case )
Of course in opposite direction the same.
_________________
Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
| Back to top |
|
|
| mq_developer |
| Posted: Thu Feb 12, 2004 5:28 pm Post subject: |
|
|
Voyager
Joined: 18 Feb 2002
Posts: 82
|
For remote administartion to work , ensure the following
1) Local qmgr ( from where runmqsc -w issued ) should be a default qmgr.
2) make sure there is a XMITQ & channels defined & connection exsisting between local qmgr and remote queue manager
3) On the remote queue manager , command server should be running and here also channels & XMITQ should be defined to send the replies back.
4) verify that channels are running back and forth , certain times channel wouldnt have been configured to startup automatically.
5) On the remote queue manager , ensure that there are no messages sent to SYSTEM.DEAD.LETTER.QUEUE , certain times due to authorization issues control message would end there ...
Also note that runmqsc -w command make use of remote put facility and sends control messages to the remote queue manager , so your XMITQs should be nothing but remote queue manager name.
Hope this helps |
|
| Back to top |
|
|
| techno |
| Posted: Thu Feb 12, 2004 8:48 pm Post subject: |
|
|
Chevalier
Joined: 22 Jan 2003
Posts: 429
|
| Code: |
| 1) Local qmgr ( from where runmqsc -w issued ) should be a default qmgr. |
I do not have any default qmgr. Although it seems logical to have a default qmgr, is there any other way to do this remote administration without having a default one!
Thanks |
|
| Back to top |
|
|
| EddieA |
| Posted: Fri Feb 13, 2004 5:15 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
No.
Or write your own using PCF messages.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| techno |
| Posted: Fri Feb 13, 2004 8:23 am Post subject: |
|
|
Chevalier
Joined: 22 Jan 2003
Posts: 429
|
| Thank you. It works fine. |
|
| Back to top |
|
|
|
|
