| Author |
Message
|
| pfarrel |
 Posted: Fri Apr 25, 2008 5:11 am Post subject: MQ Queue Manager on Tandem |
 |
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
I am running a WMQ queue manager version 5.1 on Tandem ( also known as HP non-stop, or NSK ). I am wanting to upgrade to version 5.3.
The problem I am having is getting the objects moved from the 5.1 system to the 5.3 system. saveqmgr ( MS03 ) works well on a 5.3 system, but not on a 5.1 system. MQ provides a command upgmqm, but this wants to keep the new queue manager name the same as the old, which won't work for me. |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Fri Apr 25, 2008 5:20 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Can you upgrade to the old name, run MS03, and then delete the old qmgr and create the new one? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Apr 25, 2008 5:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What issues do you have with ms03 on the 5.1 system? Does MQ 5.1 on NSK not have a command server?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| pfarrel |
| Posted: Fri Apr 25, 2008 5:37 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
Here is what I get when I run the saveqmgr client directed to a NSK 5.1 system:
c:\>cd\MS03
C:\MS03>set mqserver=SYSTEM.ADMIN.SVRCONN/TCP/172.20.1.52(1416)
C:\MS03>saveqmgrc.exe -m HPQMT2 -v 5 -o -f c:\temp8\HPQMT2.save.txt
SAVEQMGR V6.0.3
Compiled for Websphere MQ V6.0 on Aug 22 2006
With no client connection information specified.
Requesting attributes of the queue manager...
(mqutils.c) MQGET failed for reply queue. MQCC=2 MQRC=2232
C:\MS03>
This same procedure works fine when directed to an NSK 5.3 system. |
|
| Back to top |
|
|
| pfarrel |
| Posted: Fri Apr 25, 2008 5:41 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
| The suggestion of upgrading to one of the same name, then dropping it and recreating it is good, but it will require me to have the 5.1 QM down for a while in order to bring up the 5.3 system and run MS03. MS03 requires the QM you are dumping to be up. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Apr 25, 2008 5:47 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Really? A 2232? Wow...
Okay, it seems that saveqmgr isn't identifying this as a Tandem system... there's code to set MQGMO_NO_SYNCPOINT if it knows that it's running against a tandem qmgr....
Which makes sense, since you're using the client version.
Also, you almost certainly don't need the -v 5 switch. This doesn't do what you think it does.
Your two choices here are to either recompile and run it on the NSK system itself, or to use the -r switch and connect to the Tandem qmgr by way of another qmgr.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| pfarrel |
| Posted: Fri Apr 25, 2008 6:00 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
I did actually try running remotely from another QM ( connecting from AIX to Tandem ), and I received a timeout. It did put a message in the SYSTEM.ADMIN.QMGR.EVENT queue and another in the SYSTEM.DEAD.LETTER.QUEUE. The latter message shows that I got a 2035, even though the ID I'm using on AIX is the same ID that I had on the SVRCONN channel when tried the client connection. That ID is mqm. It may be that ID mqm doesn't have as much authority on a Tandem as I thought it would.
Here is what I entered on the AIX system:
mqm@lp10dev:/mqwork/ms03 $ whoami
mqm
mqm@lp10dev:/mqwork/ms03 $ saveqmgr.aix -m WBIBUXT1 -r HPQMT2 -o -f HPQMT2.save.txt
SAVEQMGR V6.0.3
Compiled for Websphere MQ V6.0 on Aug 29 2006
Requesting attributes of the queue manager...
(mqutils.c) No reply msg, make sure command server is started (strmqcsv qmgr-name)
mqm@lp10dev:/mqwork/ms03 $
Here is the resulting dead queue message on the Tandem:
4D442020 01000000 00000000 01000000 C9000000 00000000 11010000 MD ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
33030000 4D514445 41442020 00000000 00000000 414D5120 57424942 3ÂÂÂMQDEAD ÂÂÂÂÂÂÂÂAMQ WBIB
55585431 20202020 47F0CC20 20B57303 00000000 00000000 00000000 UXT1 GÂÂ ÂsÂÂÂÂÂÂÂÂÂÂÂÂÂ
00000000 00000000 00000000 00000000 53415645 514D4752 2E343746 ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂSAVEQMGR.47F
30434332 30323042 35373330 32202020 20202020 20202020 20202020 0CC2020B57302
20202020 20202020 57424942 55585431 20202020 20202020 20202020 WBIBUXT1
20202020 20202020 20202020 20202020 20202020 20202020 20202020
4D514D20 20202020 20202020 03323937 00000000 00000000 00000000 MQM Â297ÂÂÂÂÂÂÂÂÂÂÂÂ
00000000 00000000 00000000 00000006 20202020 20202020 20202020 ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
20202020 20202020 20202020 20202020 20202020 06000000 73617665 ÂÂÂÂsave
716D6772 2E616978 20202020 20202020 20202020 20202020 32303038 qmgr.aix 2008
30343235 31333530 30343931 20202020 00000000 00000000 00000000 042513500491 ÂÂÂÂÂÂÂÂÂÂÂÂ
00000000 00000000 00000000 01000000 00000000 00000000 FFFFFFFF ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
444C4820 00000001 000007F3 53595354 454D2E41 444D494E 2E434F4D DLH ÂÂÂÂÂÂÂÂSYSTEM.ADMIN.COM
4D414E44 2E515545 55452020 20202020 20202020 20202020 20202020 MAND.QUEUE
20202020 4850514D 54322020 20202020 20202020 20202020 20202020 HPQMT2
20202020 20202020 20202020 20202020 20202020 20202020 00000111 ÂÂÂÂ
00000333 4D514144 4D494E20 0000000D 5C434249 50522E24 5A333144 ÂÂÂ3MQADMIN ÂÂÂÂ\CBIPR.$Z31D
3A333937 34333835 20202020 20202020 32303038 2F30342F 31333530 :3974385 2008/04/1350
30363033 00000001 00000024 00000001 00000002 00000001 00000001 0603ÂÂÂÂÂÂÂ$ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
00000000 00000000 00000000 ÂÂÂÂÂÂÂÂÂÂÂÂ
And, here is the event message on the Tandem:
4D442020 01000000 00000000 08000000 FFFFFFFF 00000000 11010000 MD ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
33030000 4D514556 454E5420 00000000 00000000 414D5120 4850514D 3ÂÂÂMQEVENT ÂÂÂÂÂÂÂÂAMQ HPQM
54322020 20202020 0AC17363 4CAE4705 00000000 00000000 00000000 T2 ÂÂscLÂGÂÂÂÂÂÂÂÂÂÂÂÂÂ
00000000 00000000 00000000 00000000 20202020 20202020 20202020 ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
20202020 20202020 20202020 20202020 20202020 20202020 20202020
20202020 20202020 4850514D 54322020 20202020 20202020 20202020 HPQMT2
20202020 20202020 20202020 20202020 20202020 20202020 20202020
20202020 20202020 20202020 00000000 00000000 00000000 00000000 ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
00000000 00000000 00000000 00000000 20202020 20202020 20202020 ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
20202020 20202020 20202020 20202020 20202020 07000000 4850514D ÂÂÂÂHPQM
54322020 20202020 20202020 20202020 20202020 20202020 32303038 T2 2008
30343235 31333530 30363032 20202020 00000000 00000000 00000000 042513500602 ÂÂÂÂÂÂÂÂÂÂÂÂ
00000000 00000000 00000000 01000000 00000000 00000000 FFFFFFFF ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
00000007 00000024 00000001 0000002C 00000001 00000001 00000001 ÂÂÂÂÂÂÂ$ÂÂÂÂÂÂÂ,ÂÂÂÂÂÂÂÂÂÂÂÂ
000007F3 00000007 00000004 00000044 000007DF 00000000 00000030 ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂDÂÂÂÂÂÂÂÂÂÂÂ0
4850514D 54322020 20202020 20202020 20202020 20202020 20202020 HPQMT2
20202020 20202020 20202020 20202020 20202020 00000003 00000010 ÂÂÂÂÂÂÂÂ
000003FC 00000002 00000004 00000044 000007E0 00000000 00000030 ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂDÂÂÂÂÂÂÂÂÂÂÂ0
53595354 454D2E41 444D494E 2E434F4D 4D414E44 2E515545 55452020 SYSTEM.ADMIN.COMMAND.QUEUE
20202020 20202020 20202020 20202020 20202020 00000003 00000010 ÂÂÂÂÂÂÂÂ
000003FE 0000B810 00000004 00000020 00000BD1 00000000 0000000C ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ÂÂÂÂÂÂÂÂÂÂÂÂ
4D514D20 20202020 20202020 00000003 00000010 00000001 0000000D MQM ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
00000004 00000030 00000BD0 00000000 0000001C 24544553 542E5A4D ÂÂÂÂÂÂÂ0ÂÂÂÂÂÂÂÂÂÂÂÂ$TEST.ZM
51534558 452E4D51 54435052 45532020 20202020 QSEXE.MQTCPRES |
|
| Back to top |
|
|
| LouML |
| Posted: Fri Apr 25, 2008 6:02 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Apr 25, 2008 6:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
No, because this is not compiled on the NSK or running on the NSK at all.
If pfarrel wanted to compile and run on the NSK, then this could be an issue.
pfarrel... maybe you need to use 'mqm' instead of MQM..?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| pfarrel |
| Posted: Fri Apr 25, 2008 6:41 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
| Yes, I was thinking that I should be using mqm, and not MQM. I do have mqm on the SYSTEM.ADMIN.SVRCONN channel on the Tandem, which I used for the client version of saveqmgr. On my AIX system I am logged on as mqm ( not MQM ). I'm not sure why it shows as MQM in the error mesage. I was of the opinion that AIX queue managers folded IDs to lower case anyway ( not the other way around ). Any ideas where the upper case ID MQM is coming from ? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Apr 25, 2008 6:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Tandem may fold the names to UPPER case.
Also, if you used the MQSC "MCAUSER(mqm)", then this will fold to MQM, as opposed to "MCAUSER('mqm')"...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| LouML |
| Posted: Fri Apr 25, 2008 6:57 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| jefflowrey wrote: |
Tandem may fold the names to UPPER case.
Also, if you used the MQSC "MCAUSER(mqm)", then this will fold to MQM, as opposed to "MCAUSER('mqm')"... |
If I recall correctly from my old Tandem MQ days, I believe Tandem does shift unquoted names to upper case.
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Apr 25, 2008 6:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| LouML wrote: |
| If I recall correctly from my old Tandem MQ days, I believe Tandem does shift unquoted names to upper case. |
I believe it's just MQSC that does this, not specific to TANDEM.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| pfarrel |
| Posted: Fri Apr 25, 2008 7:05 am Post subject: |
|
|
Centurion
Joined: 16 Mar 2004
Posts: 120
Location: Kansas City
|
I believe that you are correct about the folding to upper case if the ID is not quoted. However I ran an alter channel and used MCAUSER('mqm') with the ID in quotes to get the lower case ID added to the SVRCONN channel, and that worked. What I am confused about is the AIX QM to NSK QM communications, where the AIX QM sends the ID in lower case.
Also, doesn't userid mqm have admin rights on Tandem, like it does on AIX ? |
|
| Back to top |
|
|
| LouML |
| Posted: Fri Apr 25, 2008 7:13 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| pfarrel wrote: |
I believe that you are correct about the folding to upper case if the ID is not quoted. However I ran an alter channel and used MCAUSER('mqm') with the ID in quotes to get the lower case ID added to the SVRCONN channel, and that worked. What I am confused about is the AIX QM to NSK QM communications, where the AIX QM sends the ID in lower case.
Also, doesn't userid mqm have admin rights on Tandem, like it does on AIX ? |
The equivilant of admin rights on a Tandem would be the SUPER.SUPER (255,255) user id.
MQ will have a userid of MQM.MANAGER (250,255). This userid should have all the rights it needs.
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude |
|
| Back to top |
|
|
|
|
