| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQ Queue Manager on Tandem |
« View previous topic :: View next topic » |
| Author |
Message
|
| jefflowrey |
 Posted: Fri Apr 25, 2008 7:14 am Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
MCAUSER replaces whatever's passed in. I was suggesting this be set on the RCVR channel on Tandem, and not on the svrconn to AIX. Also, the PUTAUT of the receiver may be impacting things.
I don't know Tandem nearly well enough to say whether or not 'mqm' is the name of the super user on that platform.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| pfarrel |
| Posted: Fri Apr 25, 2008 7:49 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
Well, I tried setting the MCAUSER on the Tandem receiver channel, but no luck.
I have a QM on AIX connected to the version 5.1 QM on Tandem, with a sender/receiver pair. On the Tandem, I set the receiver channel MCAUSER to mqm ( lower case ), and it is lower case, according to MQ/Explorer.
I ran the saveqmgr from the AIX side as follows:
saveqmgr.aix -m WBIBUXT1 -r HPQMT2 -o -f HPQMT2.save.txt
and I ended up with no response on AIX, and one message on the Tandem side in each of SYSTEM.DEAD.LETTER.QUEUE and SYSTEM.ADMIN.QMGR.EVENT. According to the dead Q message, I am getting a 2035 writing to SYSTEM.ADMIN.COMMAND.QUEUE, and the MD shows an ID of MQM ( upper case ). Strange ! |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Apr 25, 2008 7:52 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Maybe Tandem does fold all users to UPPERCASE, somehow, at least in MQ v5.1...
Maybe MQM is the wrong user anyway?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Fri Apr 25, 2008 11:04 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
It has been a really long time since I worked on a Tandem, and my old Tandem documentation is at home somewhere.... so this is just a shot in the dark.
If I were you, I would create a local user on your Windows machine (I see a "c" prompt in one of your posts, so I'm assuming Windows) called mqm.manager and put it in the local mqm group. (The passord, of course, is irrelevant except to the local OS.) Then I'd do a 'contact admin' mqm.manager for the command prompt and try MS03 again.
If that failed with a 2035, I would then try a local user ID called MQM.MANAGER.
As I recollect, the login name is the user.group..... not just the user.
 |
|
| Back to top |
|
|
| LuisFer |
| Posted: Mon May 05, 2008 10:42 am Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
I have the MS03 compiled/NLD for v51 on NSK for Guardian (G06.26), working fine. 
If you want it , on private msg, give me your email
Regards |
|
| Back to top |
|
|
| LuisFer |
| Posted: Mon May 05, 2008 11:12 am Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
| pfarrel wrote: |
| ... getting a 2035 writing to SYSTEM.ADMIN.COMMAND.QUEUE, and the MD shows an ID of MQM ( upper case ). Strange ! |
No strange the mqm.manager user belongs to the MQM group use the dspmqusr -m <QMgrName> to display the users and groups |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
