|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Preventing Inadvertent Queue Manager Migration to v7.5 |
« View previous topic :: View next topic » |
Author |
Message
|
SAFraser |
Posted: Wed Nov 06, 2013 3:15 pm Post subject: Preventing Inadvertent Queue Manager Migration to v7.5 |
|
|
 Shaman
Joined: 22 Oct 2003 Posts: 742 Location: Austin, Texas, USA
|
We are planning a multi-stage migration from MQ v7.0.1.9 to v7.5.0.2. We have 10 queue managers on each Solaris host (these hosts are dedicated to MQ; no applications run on these hosts).
This is what I understand, please correct me as I hope I am wrong.
Using crtmqenv to fetch the values, I have created two profiles. One profile, when sourced, creates a v7.0 environment and the other, when sourced, creates a v7.5 environment.
When we (MQ admins) log in, we will default to v7.0. We will change back and forth between environments by sourcing the appropriate profile.
I've even included a reference in the prompt to help us know the profile we are using:
newMQ-mqm:/export/home/mqm>
oldMQ-mqm:/export/home/mqm>
Is there a danger here? Seems to me that if I am in the v7.5 environment and I mistakenly strmqm a v7.0 queue manager, I will have invoked the Inadvertent Migration Feature.
Is my understanding correct? How have others dealt with this? Thanks. |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Nov 07, 2013 8:12 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Change the start script to first call
setmqenv -m <qmgrname>
This way you should always start the qmgr in the right mqenvironment.
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
markt |
Posted: Thu Nov 07, 2013 10:39 am Post subject: |
|
|
 Knight
Joined: 14 May 2002 Posts: 508
|
Look at the setmqm command. A queue manager is "owned" by an installation. So if you try to strmqm a V7.1 qmgr from the V7.5 binaries it will fail until you have explicitly done the setmqm. |
|
Back to top |
|
 |
rammer |
Posted: Thu Nov 07, 2013 11:02 am Post subject: |
|
|
Partisan
Joined: 02 May 2002 Posts: 359 Location: England
|
We created a new user ID mqm75 that has setmqenv in the profile for 7.5
mqm is the default installation for version 7.
If I was doing it again not sure I would have bothered with the mqm75 user id, and rather just stick with the setmqenv command to switch between versions.
There is also this file from IBM to automatically switch between env's. I havent had chance to look properly at it yet
http://www-01.ibm.com/support/docview.wss?uid=swg21587504 |
|
Back to top |
|
 |
SAFraser |
Posted: Thu Nov 07, 2013 1:00 pm Post subject: |
|
|
 Shaman
Joined: 22 Oct 2003 Posts: 742 Location: Austin, Texas, USA
|
I am building our POC. I have been reading, planning, and documenting as I go.
I will try your suggestions in our POC. I am very appreciative of these ideas. Thanks so very much!
PS If I try that IBM script, I'll let you know how it works for us. |
|
Back to top |
|
 |
fjb_saper |
Posted: Sat Nov 09, 2013 2:18 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
SAFraser wrote: |
I am building our POC. I have been reading, planning, and documenting as I go.
I will try your suggestions in our POC. I am very appreciative of these ideas. Thanks so very much!
PS If I try that IBM script, I'll let you know how it works for us. |
The -z switch did not work for me on Windows... (note the wmqprofile is only written for Unix operating systems.)
The -z switch to setmqenv is ignored in windows...
\path to highest inst binaries\setmqenv -m <qmgr> works for me in windows...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|