Hi Doug,

it is impossible to use mqm as a userid on Windows, because Windows does 
not allow you to have the same name for both a group and a user, and mqm 
is mandated as the name of a group when you install MQSeries.

So, to get this to work, you need to use your own user on unix (make it a 
member of the mqm group) and run the command from there. Then on the 
Windows system, create the same userid, and make it a member of the mqm 
group on Windows as well.

That should work, but is potentially exposing some worrying security holes 
unless you have really strong controls around SSL channels (or security 
exits) and MCAUSERs.

Regards,

Neil Casey
Lead Technical Specialist, Middleware MQ Support
Technology Operations
National Australia Bank

Level 1, 122 Lewis Rd  (Mon Fri)
Tel: +61 (0) 3 9886 2375  |  Fax: +61 (0) 3 9886 2700  |  Mob: +61 (0) 408 
356 208
Pier 4, Level 8, 800 Bourke St  (Tue Wed Thu)
Tel: +61 (0) 3 8634 2205  |  Fax: +61 (0) 3 8634 3788  |  Mob: +61 (0) 408 
356 208
Email: [EMAIL PROTECTED]




"Clark, Douglas" <[EMAIL PROTECTED]> 
Sent by: MQSeries List <MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT>
01/05/2007 09:53
Please respond to
MQSeries List <MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT>


To
MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT
cc

Subject
Re: ms03 (saveqmgr) v6.0.3 update






I have gone through and tracked down my environment.  All MQSeries objects 
are set as specified.  I was able to capture the PCF formatted message and 
view it which showed that the assigned UserId is mqm which does not exist 
on my windows server.  The windows server already has a group setup named 
mqm.  Any suggestions?
 

From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf 
Of Neil Casey
Sent: Thursday, April 26, 2007 3:18 PM
To: MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT
Subject: Re: ms03 (saveqmgr) v6.0.3 update


Hi Doug, 

MQRC 2087 means unknown remote queue manager. 

I think that ms03 saveqmgr is connecting to the local queue manager, and 
then trying to send PCF commands to the target queue manager via normal MQ 
mechanisms. This means you either need a queue manager alias to point to 
the other queue manager, or you need the transmission queue named with the 
queue manager name, or the two queue managers need to be in a cluster. 

You will also need the same type of mechanism in the opposite direction so 
that the PCF responses can be directed back to your ms03 instance. 

Regards,
Neil Casey 
Lead Technical Specialist, Middleware MQ Support 
Technology Operations 
National Australia Bank 

Level 1, 122 Lewis Rd 
Tel: +61 (0) 3 9886 2375  |  Fax: +61 (0) 3 9886 2700  |  Mob: +61 (0) 414 
615 334 
Email: [EMAIL PROTECTED]




"Clark, Douglas" <[EMAIL PROTECTED]> 
Sent by: MQSeries List <MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT> 
04/27/2007 07:11 AM 

Please respond to
MQSeries List <MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT>



To
MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT 
cc

Subject
Re: ms03 (saveqmgr) v6.0.3 update








I am trying to run SAVEQMGR V6.0.3 but I fail connecting to Windows
systems.  I don't see any errors and would appreciate any assistance I
can get to figure this out.

The problem occurs only when I try and retrieve data from remote Windows
queue managers.  When I request the data as a local request on the
windows server it runs fine.  When I issues the request from and AIX
server or a Windows server to a remote AIX server it works fine.  But
when from Windows or AIX I try and retrieve the data from a Windows
server I keep getting "(mqutils.c) MQOPEN failed for
SYSTEM.ADMIN.COMMAND.QUEUE, CC=2 RC=2087"  I can't find what I am
missing.

Doug 

-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] On
Behalf Of Wayne Schutz
Sent: Tuesday, September 05, 2006 8:53 AM
To: MQSERIES@LISTSERV.MEDUNIWIEN.AC.AT
Subject: ms03 (saveqmgr) v6.0.3 update

MS03 (saveqmgr) has been updated onto the supportpac page:
http://www-1.ibm.com/support/docview.wss?rs=171&q1=mA1J&uid=swg24000673&;
loc=en_US&cs=utf-8&lang=en


Final list of changes:
NEW IN THIS RELEASE
The following changes have been made in this release:
* -z (-Z) option to generate setmqaut commands.
* Fixed small bug where rc from MQGET was being hidden by check for
MQADMIN message.
* Added options to -R (create reset commands) to allow specifications of
the TYPES of channels to reset.
* Fixed problem with 'oneLine (-1)' and chained exits. Also trim extra
space off back of chained exits.
* iSeries didn't like qmgr names starting with numeric.
* Added additional options on the QSAVEQMGR.CMD panel.
* If a bad CLWLUSEQ value is returned by the cmd server, we write an
error message and set the value to "QMGR".

Wayne M. Schutz, Senior Solutions Architect, IBM Software Services for
WebSphere
(cell) 914-213-9021
Internet: wschutz @ us.ibm.com
(sent from Linux)
IBM Certified Solution Designer - WebSphere MQ v5.3, IBM Certified
Systems Administrator - WebSphere  MQ v6, IBM Certified Solution
Developer  - WebSphere v5.3 IBM Certified Solution Designer - WebSphere
Message Broker, IBM Certified Solutions Expert - MQSeries Integrator,
IBM Certified System Architecture and Design - MQSeries Integrator V2

To unsubscribe, write to [EMAIL PROTECTED] and,
in the message body (not the subject), write: SIGNOFF MQSERIES
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

National Australia Bank Ltd - ABN 12 004 044 937
This email may contain confidential information. If you are not the 
intended recipient, please immediately notify us at [EMAIL PROTECTED] 
or by replying to the sender, and then destroy all copies of this email. 
Except where this email indicates otherwise, views expressed in this email 
are those of the sender and not of National Australia Bank Ltd. Advice in 
this email does not take account of your objectives, financial situation, 
or needs. It is important for you to consider these matters and, if the 
e-mail refers to a product(s), you should read the relevant Product 
Disclosure Statement(s)/other disclosure document(s) before making any 
decisions. If you do not want email marketing from us in future, forward 
this email with "unsubscribe" in the subject line to 
[EMAIL PROTECTED] in order to stop marketing emails from this 
sender. National Australia Bank Ltd does not represent that this email is 
free of errors, viruses or interference.


List Archive - Manage Your List Settings - Unsubscribe 
Instructions for managing your mailing list subscription are provided in 
the Listserv General Users Guide available at http://www.lsoft.com 


List Archive - Manage Your List Settings - Unsubscribe 
Instructions for managing your mailing list subscription are provided in 
the Listserv General Users Guide available at http://www.lsoft.com 


National Australia Bank Ltd - ABN 12 004 044 937
This email may contain confidential information. If you are not the intended 
recipient, please immediately notify us at [EMAIL PROTECTED] or by replying to 
the sender, and then destroy all copies of this email. Except where this email 
indicates otherwise, views expressed in this email are those of the sender and 
not of National Australia Bank Ltd. Advice in this email does not take account 
of your objectives, financial situation, or needs. It is important for you to 
consider these matters and, if the e-mail refers to a product(s), you should 
read the relevant Product Disclosure Statement(s)/other disclosure document(s) 
before making any decisions. If you do not want email marketing from us in 
future, forward this email with "unsubscribe" in the subject line to [EMAIL 
PROTECTED] in order to stop marketing emails from this sender. National 
Australia Bank Ltd does not represent that this email is free of errors, 
viruses or interference.

To unsubscribe, write to [EMAIL PROTECTED] and,
in the message body (not the subject), write: SIGNOFF MQSERIES
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