| Author |
Message
|
| LouML |
 Posted: Tue Aug 28, 2007 7:16 am Post subject: Migration to 6.0.2 question |
 |
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
Please forgive the newbie questions.
I just recently took responsibility for MQ in our Solaris environment. Unfortunately, we are running various levels of MQ (5.0, 5.1, 5.3.12). Of course we need to upgrade to 6.0.2 ASAP.
What are the benefits of migrating a queue manager versus deleting and creating a new queue manager (after having saved all defined objects using saveqmgr)?
Also, do we have to migrate (or reinstall) the MQ clients to 6.0.2 at the same time as the MQ server? Or can an 5.3 client still function connecting to a 6.0.2 server? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Aug 28, 2007 7:32 am Post subject: Re: Migration to 6.0.2 question |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| LouML wrote: |
| What are the benefits of migrating a queue manager versus deleting and creating a new queue manager (after having saved all defined objects using saveqmgr)? |
A clean start? I'm also unconvinced migration from before v5.3 will be entirely successful.
If you've just taken over, redefining will give you a clearer picture of the set up and more control. A baseline if you will.
| LouML wrote: |
Also, do we have to migrate (or reinstall) the MQ clients to 6.0.2 at the same time as the MQ server? Or can an 5.3 client still function connecting to a 6.0.2 server? |
MQv5.3 clients work fine with v6 servers. Naturally it's an advantage to move these as well as time permits.
You've really still got v5.0? Do you mean z/OS v5.0?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| LouML |
| Posted: Tue Aug 28, 2007 7:53 am Post subject: Re: Migration to 6.0.2 question |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| Vitor wrote: |
| You've really still got v5.0? Do you mean z/OS v5.0? |
Yeah, as far as I can tell. I'm not sure how to tell what version I have. I tried mqver but it does not work on this particular box. I did a cat on an FFST file and see 500 under LVLS. I assume that means version 5.0:
| Code: |
bash-2.02$ cat /var/adm/mqm/errors/AMQ07109.0.FDC
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Tuesday August 21 08:00:04 EDT 2007 |
| Host Name :- emsg1 |
| PIDS :- 5765B75 |
| LVLS :- 500 |
| Product Long Name :- MQSeries for Sun Solaris 2 (Sparc) |
| Vendor :- IBM |
| Probe Id :- XC130001 |
| Application Name :- MQM |
| Component :- xehExceptionHandler |
| Build Date :- Feb 17 1999 |
| UserID :- 00000886 (etf) |
| Program Name :- etf_trades.pl |
| Process :- 00007109 |
| Thread :- 00000000 |
| Major Errorcode :- xecSTOP |
| Minor Errorcode :- OK |
| Probe Type :- HALT6109 |
| Probe Severity :- 1 |
| Probe Description :- AMQ6109: An internal MQSeries error has occurred. |
| |
+-----------------------------------------------------------------------------+
No MQM Function Stack Available
bash-2.02$ |
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 28, 2007 8:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You're probably better off deleting and recreating a v5.0.0 qmgr, than to try and migrate it to v6.
It should work, but it's probably safer not to.
You can connect v5.3 clients to a v6.0.x qmgr. But there are issues with some levels of v5.3 clients (for java) talking to higher versions of MQ (even higher revisions of v5.3).
So, again, it's safer to upgrade the clients.
It's also better, in general, to go through and blow out all the dust bunnies in your enterprise, and find out what dragons they've been hiding. From a risk management perspective, that is.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| LouML |
| Posted: Tue Aug 28, 2007 10:43 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
Thanks for the input fellas.
I feel a fresh install is the best option for me. As mentioned, it will give me a chance to clean out any unused objects and get a better grip on what I have.
Just a follow up - I'm preparing to start notifying the application teams about the upgrade. It doesn't look to me that there should be any application programming changes or re-compiles needed. Am I correct in assuming that their programs *should* run as is? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 28, 2007 10:48 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| LouML wrote: |
| Am I correct in assuming that their programs *should* run as is? |
Ought to, but you've been running against some very old versions. A comprehensive test plan will provide reasurance. 
Engage them with the prospect of all the shiny new features they'll be able to misuse. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| LouML |
| Posted: Tue Aug 28, 2007 11:02 am Post subject: |
|
|
Partisan
Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY
|
| Vitor wrote: |
| LouML wrote: |
| Am I correct in assuming that their programs *should* run as is? |
Ought to, but you've been running against some very old versions. A comprehensive test plan will provide reasurance.
Engage them with the prospect of all the shiny new features they'll be able to misuse. |
Actually, we only have one server running 5.0 and 3-4 running 5.1. The bulk of them are running 5.3.12 so we might not be as bad off as I first thought. Frankly, I'm not even sure if the older servers will make the cut. There is talk of application consolidation and/or elimination. Certainly, I'll be starting with the easiest/most stable boxes.
I'm tempted to just do it over a weekend without notice and then put out whatever fires erupt on Monday 
(Of course, I won't do that - but it's tempting) |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 28, 2007 1:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| LouML wrote: |
I'm tempted to just do it over a weekend without notice and then put out whatever fires erupt on Monday
|
The Big Bang implementation strategy... 
_________________
Honesty is the best policy.
Insanity is the best defence.
Last edited by Vitor on Wed Aug 29, 2007 6:56 am; edited 1 time in total |
|
| Back to top |
|
|
| UglyAngelX |
| Posted: Wed Aug 29, 2007 6:50 am Post subject: |
|
|
Voyager
Joined: 04 Dec 2001
Posts: 90
Location: BEARS FAN IN STEELER COUNTRY
|
| Personally I could not see the older servers making the cut...due to requirements. Would be strange to be upgrading everything on a server, besides MQ, so I am assuming those servers on anything below 5.3 are old servers waiting to be put out ot pasture. We have run into several problems with running Client 5.3 with our Solaris servers, so as a standard we make everyone move to Client V6 when we make the moves. As far as installs....we have migrated (V5.3.x) some and done some clean installs and had no issues noted. Clustering is the only thing that has bitten us in the arse once or twice during migration/clean installs. If you have clusters, be certain you have solid procedures setup! |
|
| Back to top |
|
|
|
|
