ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Using RUNMQSC to remote QMGR problem

Post new topic  Reply to topic
 Using RUNMQSC to remote QMGR problem « View previous topic :: View next topic » 
Author Message
smeunier
PostPosted: Mon Oct 18, 2010 9:39 am    Post subject: Using RUNMQSC to remote QMGR problem Reply with quote

Partisan

Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont

I'm trying to query queues on a remote queue manager using RUNMQSC. I have read and understood the documentation on how to do this and have tried to do it with little success.

The test environment I'm trying to do this on is to run the RUNMQSC command from a AIX MQ V6.0.9 environment to another AIX server running the same MQ version level.

Sender/Receiver channels are set up and running, transmission queue defined with the name of the remote queue manager, and command server is running on the target server.

I execute the command:

Code:

runmqsc -w 30 DTEMQHUB2 < testmqs


DTEMQHUB2 is the remote queue manager
testmqs is a file conatining one command: DISPLAY QL(ABC) all

The output is:
Code:


runmqsc -w 30 DTEMQHUB2 < testmqs
5724-H72 (C) Copyright IBM Corp. 1994, 2005.  ALL RIGHTS RESERVED.
Starting MQSC for queue manager DTEMQHUB2.


AMQ8146: WebSphere MQ queue manager not available.

No MQSC commands read.
0 command responses received.


I'm not sure what to make of this, as I have verified all target components are operational.

Any experience on this? The command is being run from the mqm id.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Oct 18, 2010 10:03 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Have you verified following points:
  • On the AIX box you are running runmqsc on you have a default qmgr
  • The default qmgr has a default way of communications with the target qmgr and vice versa. This is usually achieved with an xmitq in the target qmgr name or a corresponding qmgr alias.


Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
JosephGramig
PostPosted: Mon Oct 18, 2010 10:08 am    Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA

It is telling you it cannot resolve the QMGR DTEMQHUB2. Do you have channels to that QMGR?

Here is an example of mine where I'm issuing a refresh to a PR remote to the QMGR at the machine where I'm issuing the command:

echo 'REFRESH CLUSTER(PROD) REPOS(YES)' |runmqsc -w 30 MONKEYDO

The command is going through the Default QMGR. Use the -m option (might be a V7 thing) if you don't have a default QMGR.

http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.amqzag.doc/fa15950_.htm
Back to top
View user's profile Send private message AIM Address
smeunier
PostPosted: Mon Oct 18, 2010 10:37 am    Post subject: Reply with quote

Partisan

Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont

Took a while to find this......but the queue managers were not created as default queue managers (tsk tsk).....this was identified by the absence of the DefaultQueueManager stanza in the mqs.ini file. I'll see if I can get that updated and retry and report back.
Back to top
View user's profile Send private message
gbaddeley
PostPosted: Tue Oct 19, 2010 2:52 pm    Post subject: Reply with quote

Jedi Knight

Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia

smeunier wrote:
Took a while to find this......but the queue managers were not created as default queue managers (tsk tsk).....this was identified by the absence of the DefaultQueueManager stanza in the mqs.ini file. I'll see if I can get that updated and retry and report back.


There are valid business arguments for NOT defining a default queue manager, so its not necessarily a case of tsk tsk.
_________________
Glenn
Back to top
View user's profile Send private message
Michael Dag
PostPosted: Thu Oct 21, 2010 2:11 am    Post subject: Reply with quote

Jedi Knight

Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)

smeunier wrote:
Took a while to find this......but the queue managers were not created as default queue managers (tsk tsk).....this was identified by the absence of the DefaultQueueManager stanza in the mqs.ini file. I'll see if I can get that updated and retry and report back.


if you are on MQ V7 you can use -m Queuemanager flag with runmqsc if no default queuemanager exists...

see http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.amqzag.doc/fa15950_.htm
_________________
Michael



MQSystems Facebook page
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Using RUNMQSC to remote QMGR problem
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.