| Author |
Message
|
| sbuckman1 |
 Posted: Fri Sep 02, 2011 11:54 am Post subject: Issue an MQ Admin command (runmqsc) when not in mqm group |
 |
|
Newbie
Joined: 15 Apr 2006
Posts: 7
Location: Springfield, VA
|
Platform=Solaris Version 7.0.1.5
special application id (not defined in the mqm group) needs to be able to issue "suspend qmgr .." and "resume qmgr ..." commands as part of its automation.
I have been attempting to set the authorization via the setmqaut commands without success.
Was wondering if this is an execuatble permissions issue, or even possible if not defined to mqm group.
I can work around this by utilizing an mqclient connection (with a hardcoded mcauser) but would really like to make it 'clean' .. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri Sep 02, 2011 5:56 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Why would you need (automation) to suspend and resume a qmgr?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Sep 02, 2011 6:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
besides answering bruce2359's question, have considered a script with sudo? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sbuckman1 |
| Posted: Sat Sep 03, 2011 3:27 am Post subject: |
|
|
Newbie
Joined: 15 Apr 2006
Posts: 7
Location: Springfield, VA
|
I am in a HA environment - The front end application (I support it, didnt write it!) is capable of only connections to a single host, and any replies have to be returned to the active connection.
During maintenance, we move this application to an alternate host/Qmgr - hence the need for suspend/resume, to not orphan messages.
I know how to do workarounds to my question - I am just looking for a direct way of doing it. Hence my question to the forum. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Sep 03, 2011 4:15 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So your queue managers are HA and your applications are HA and you're using an MQ Cluster.
You shouldn't suspend and resume the queue manager from the MQ Cluster.
You should share and unshare the application queues instead. This is the *best* way to handle your situation.
You should entirely be able to do either set of operations - suspend/resume qmgr or alter qlocal - from a non-mqm user. But you will probably need to do so using PCF messages and not runmqsc, and you will need to provide the relevant and necessary permissions to the various objects including the command queue.
If you're uncomfortable with writing code to send PCF messages, when you are simply trying to "script* a solution, you should look at the Perl modules for MQ - SupportPac MA89. They work quite a treat and install using CPAN from Unix without any trouble. |
|
| Back to top |
|
|
| sbuckman1 |
| Posted: Sat Feb 04, 2012 9:12 am Post subject: Issue an MQ Admin command (runmqsc) when not in mqm group |
|
|
Newbie
Joined: 15 Apr 2006
Posts: 7
Location: Springfield, VA
|
As a followup / closure to this thread, I have chosen to utilize queue disable/enable(put) to manage traffic flow. This has proven to be 99% effective - still get the occasional message in the DLQ, but this is manageable.
Am now exploring use of the Multi-Instance Qmgr setups..
Thanks for the advice.  |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Feb 04, 2012 3:02 pm Post subject: Re: Issue an MQ Admin command (runmqsc) when not in mqm grou |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| sbuckman1 wrote: |
As a followup / closure to this thread, I have chosen to utilize queue disable/enable(put) to manage traffic flow. This has proven to be 99% effective - still get the occasional message in the DLQ, but this is manageable.
Am now exploring use of the Multi-Instance Qmgr setups..
Thanks for the advice. |
Exactly what problem did you resolve by put enable/disable?
Why were/are messages going to the DLQ?
What does put enable/disable have to do with messages going to the DLQ?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Feb 04, 2012 9:08 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Sometime after the Put Disable an app on another QM sends a message addressed specifically to this queue on this queue manager. When it arrives at this QM, it gets placed in the DLQ.
Suspending a QM or put disabling the queue does not 100% prevent messages from being sent to this QM.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
