The command server will use the userid in the message to perform access
checks. If you switch on authority events presumably you'll see an
authority event explaining the problem. But essentially it just sounds like
user2 hasn't got the authority to issue the DIS QMGR command.

By the way; if you have a client channel available you could try my MO72
SupportPac and at least remove the Sender/Receive from the problem,

Cheers,
P.

Paul G Clarke
WebSphere Messaging Clients
IBM Hursley




                                                                           
             "Coombs,                                                      
             Lawrence"                                                     
             <[EMAIL PROTECTED]                                          To 
             COM>                      [email protected]  
             Sent by: MQSeries                                          cc 
             List                                                          
             <[EMAIL PROTECTED]                                     Subject 
             V.MEDUNIWIEN.AC.A         Re: Remote Administration using the 
             T>                        Command Server                      
                                                                           
                                                                           
             12/04/2006 18:38                                              
                                                                           
                                                                           
             Please respond to                                             
               MQSeries List                                               
                                                                           
                                                                           




Does anyone know if the Command Server uses alternate user security? I
setup a simple test as follows:

1. On an AIX box I start a queue manager (QM1) and its command server.

*
             I add user2 to the mqm group, but not user1 (I was lazy)


2. On Windows machine for user 1

*
             I open a command prompt (DOS window)
*
             I start a queue manager (defined as the default queue manager)
*
             I issue the command:  runmqsc -w 30 QM1 followed by

                                          dis qmgr all

** The command always timeout. A message is put to the DLQ on MQ1 with a
2035 reason code.

3. On Windows machine for user 2

*

             I open a command prompt (DOS window)
*
             I start a queue manager (defined as the default queue manager)
*
             I issue the command runmqsc -w 30 QM1 followed by

                                          dis qmgr all

It always works on user2's workstation but not user1. Am I right in
assuming that the command server is using alternate user security?

PS: the connectivity between the queue managers work.

Lawrence Coombs, Data Integration
Sears Holdings Corporation
IT Specialist, SR0704OASM
3333 Beverly Road (G2-308B)
Phone: 1.847.286-3064
Page:   1.800.759-8888 Pin# 7271860 (1-way)
E-mail:  [EMAIL PROTECTED]

________________________________

From: MQSeries List on behalf of AkBar E. Dar
Sent: Wed 4/12/2006 12:11 PM
To: [email protected]
Subject: Re: MQ Registry Information Gone



(See attached file: AMQERR03.LOG)(See attached file: AMQERR01.LOG)(See
attached file: AMQERR02.LOG)
Thanks,

AkBar E. Dar
The United Illuminating Company
New Haven, CT
Off: (203) 499-5981
Cell: (203) 623-9270

---------------------------------------------------------
This e-mail, and any attached file(s), is intended solely for the use of
the individual or entity to whom this e-mail is addressed and may contain
information that is privileged, confidential or exempt from disclosure. If
you are not one of the named recipient(s) or otherwise have reason to
believe that you have received this message in error, please notify the UI
Information Security Manager at 203-499-3689 and delete this message
immediately from any computer. Any other use, retention, dissemination,
retransmission, printing or copying of this e-mail is strictly prohibited.
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com

Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html



-----------------------------------------
This message, including any attachments, is the property of Sears
Holdings Corporation and/or one of its subsidiaries. It is
confidential and may contain proprietary or legally privileged
information. If you are not the intended recipient, please delete
it without reading the contents.  Thank you.


Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Reply via email to