| Author |
Message
|
| mpong |
 Posted: Tue Aug 31, 2010 1:03 am Post subject: MQ upgradation 5.3 to 6 or 7 |
 |
|
Disciple
Joined: 22 Jan 2010
Posts: 164
|
Hi, we have 3 windows servers which run on MQ 5.3 and another 2 runs on MQ 6.
Our 5.3 servers are transport less no of messages; I feel we don’t need to upgrade since it is not getting frequent messages.
Is there any way that we can find out life time exits for MQ 5.3 based on something??
I have told them let it run as long as it can, we will upgrade once it fail.
Pls suggest some solution.
Regards. |
|
| Back to top |
|
 |
| dgolding |
| Posted: Tue Aug 31, 2010 2:42 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
This post should be terminated with prejudice for two reasons:
Only moderators should post, relevant to frequently asked questions - not specific queries like here;
Anybody who uses the term "upgradation" should be taken out the back and shot.  |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Aug 31, 2010 2:50 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
I'll add to that (whilst also moving it), any WMQ Admin that advocates "...I feel we don’t need to upgrade since it is not getting frequent messages..." and "...I have told them let it run as long as it can, we will upgrade once it fail..." should be taken out the back and shot thrice
You might want to try either of the current Info Centres, which contain links to the WebSphere MQ Support web page, where you will find the product life-cycle information you seek.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 31, 2010 4:13 am Post subject: Re: MQ upgradation 5.3 to 6 or 7 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mpong wrote: |
| I feel we don’t need to upgrade since it is not getting frequent messages. |
And if the messages that travel infrequently contain vital business data? $1m order for something? Tax data for the government without which they'll shut you down?
| mpong wrote: |
| I have told them let it run as long as it can, we will upgrade once it fail. |
How long will it take you to do the upgrade? What happens if they want to actually do some business while you're upgrading? What happens if the hardware (which is presumably of the same age) needs upgrading to support the new version? Will you tell them "Hey, well, sucks to be you"?
| mpong wrote: |
| Is there any way that we can find out life time exits for MQ 5.3 based on something?? |
WMQv5.3 is already out of support so in the event of any problem your only recourse is to update. If you want to be more specific about the "something" we might be able to advise further.
If you mean "how long will the v5.3 servers run?" they'll run until something changes that upsets the balance; network change, OS patch, non-WMQ software upgrade, application change somewhere in the estate.
| mpong wrote: |
| Pls suggest some solution. |
Don't just sit there waiting for something to break. Do some work and prevent it breaking.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| cronydude |
| Posted: Tue Aug 31, 2010 7:57 am Post subject: |
|
|
Voyager
Joined: 11 Nov 2001
Posts: 85
Location: US
|
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Aug 31, 2010 8:02 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Yeesh.
So we need to shoot these people too, and stop the rot spreading. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Aug 31, 2010 8:43 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Now that we've pounded the OP for his/her English skills, let's focus on the issue of maintenance/upgrade.
I've encountered two distinct schools of thought: 1) don't do maintenance or upgrades until a catastrophic failure occurs; and 2) do maintenance and upgrades to avoid catastrophic failures.
What is required is a cost/benefit analysis. Presuming that the messages that flow through mq are of some business value, what will be the cost if/when there is an outage? How long an outage can be tolerated? What tools/methods/sources will be available to recover from the outage?
Since v5 is no longer supported, do you intend to install, test and go live with v7 when the failure occurs? What time-frame will this take?
Once the cause of the outage is identified (something fixed in v6 or v7), will your career survive the inevitable question: why didn't you (we) know about this possibility? And why didn't you (we) do anything before the failure occurred?
Consider that most organizations do tune-ups on their vehicles, re-paint their buildings, replace/repair office furniture and equipment. Why would you do less for computer hardware/software?
I can guess at the answer to this questions: Does your organization have a business continuation (disaster recovery) plan? If so, has it been tested?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Aug 31, 2010 4:24 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
| I've encountered two distinct schools of thought: 1) don't do maintenance or upgrades until a catastrophic failure occurs; and 2) do maintenance and upgrades to avoid catastrophic failures. |
Another school of thought is that once a server comes on line and it is stable for a long period, there is a risk that applying maintenance or upgrades could reduce its stability. Its certainly disruptive and costs $$$ to coordinate and implement.
I have seen ancient SunOS servers running critical applications on MQ 5.2 that haven't been touched in years. "If it ain't broke don't fix it". Sooner or later there will be a catastrophic failure (most likely a hard disk, NIC or other hardware), and the apps accept that risk and will invest the $$$ when it occurs. With any luck, the server will last the life of the application (~10 years?) before it is replaced by newer technology, and it can be decomissioned.
BTW, I don't agree with this mentality.
_________________
Glenn |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Aug 31, 2010 4:28 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| gbaddeley wrote: |
| BTW, I don't agree with this mentality. |
I don't disagree... exactly... as long as you do not do anything to the box.
ESPECIALLY any upgrades to the application itself.
If there is no business reason to ever change the application again, then, sure. Leave everything exactly as it is and wait for it to fail over.
But if the business requirements are actually that static... then it's time to look for a new job. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Aug 31, 2010 5:16 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| But if the business requirements are actually that static... |
Static today may be something different tomorrow.
Software maintenance brings resolutions to known problems. Upgrades bring new capabilities.
There is risk from not changing; and there is risk from changing.
I've had clients that were of the 'if it works, don't change it' school of thought. Of course, in real life, they get their cars tuned and the oil changed regularly; they paint their homes; they repair/replace office furniture and equipment; buy new underwear (or at least wash and mend what they have)...
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Sep 01, 2010 6:22 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| bruce2359 wrote: |
Software maintenance brings resolutions to known problems. Upgrades bring new capabilities.
|
And upgrades introduce new bugs, hopefully none that impact your particular set up.
| bruce2359 wrote: |
There is risk from not changing; and there is risk from changing.
|
Amen.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
