| Author |
Message
|
| dogbert64 |
 Posted: Mon Jun 04, 2007 12:24 pm Post subject: How to upgrade MQ Client 5.3 --> 6.0? |
 |
|
Acolyte
Joined: 11 Jun 2003
Posts: 58
|
I am in the process of bringing all our MQ installs from 5.3 to 6.0. From what I read, it might be best to do the MQ Clients first, and then the queue managers after that.
All the MQ Clients we have are at 5.3 version (althought differerent CSD levels) and run on Windows.
My question is this: How do I get from the MQ Clients v5.3 to v6.0? Do I:
1) Uninstall the 5.3 clients, reboot (it's Windows after all) and then install the 6.0 clients.
2) Upgrade the 5.3 clients in place by running the 6.0 install which will recognize the 5.3 clients and upgrade them and then reboot.
Thanks in advance, |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jun 04, 2007 11:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I'd go with 2, but wouldn't put this as a priority. I'm not aware of any functional differences between v5.3 & v.6 clients, and the v5.3 clients run perfectly happily again v6 queue managers.
Indeed, the v6 client connects fine to a v5.3 queue manager, as one of the developers accidently discovered to his surprise a few days ago here! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jun 05, 2007 2:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Please upgrade v5.3 clients to at least CSD13 - and preferrably to v6 - particularly when talking to v6 qmgrs.
It is entirely likely that at least some of your clients are actually at CSD8, 9 or 10 of v5.3, and thus subject to failure.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Jun 05, 2007 2:23 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Failure? For what reasons?
The only problem we have found with v5.3 clients used with higher level queue managers is an obscure JMS MQOPEN issue. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jun 05, 2007 2:36 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
| It is entirely likely that at least some of your clients are actually at CSD8, 9 or 10 of v5.3, and thus subject to failure. |
We've got v5.3 clients that have sat in dusty corners for some time and are still working. While I accept the general principle of upgrade sooner rather than later, what problems do you forsee?
And I'd still prioritise getting the queue managers onto the latest release, as this will resolve / prevent more problems faster than rolling out the client.
My personal view, other opinions may be equally valid, etc.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jun 05, 2007 2:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Past behavior is no guarantee of future success...
CSD 8 and 9 of v5.3 are officially withdrawn for known issues communicating with higher level qmgrs.
That one client sitting at CSD5 of v5.3, "dusty, but still working" is likely the one app you should have actually upgraded to v6 first. It's likely a business critical application that hasn't received any significant maintenance of any kind in several years and thus has a very high likelyhood of silent and mysterious failure. The risks of that failure being catastrophic are proportionate to the magnitude of the catastrophy.
Dust bunnies in the enterprise should be clearly marked "Here be dragons".
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jun 05, 2007 2:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
| That one client sitting at CSD5 of v5.3, "dusty, but still working" is likely the one app you should have actually upgraded to v6 first. It's likely a business critical application that hasn't received any significant maintenance of any kind in several years and thus has a very high likelyhood of silent and mysterious failure. The risks of that failure being catastrophic are proportionate to the magnitude of the catastrophy. |
It's (perhaps alarmingly) a number of clients sitting at v5.3, all used by business critical applications subject to ongoing development on a rolling cycle. New code rolls out every 6 weeks or so, and yes, we are planning to roll out v6 clients but it's on the plan for after the rest of the queue managers have been done.
For what it's worth, the queue managers are after the brokers but that's because we really, really need to get rid of v2.1 quickly! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jun 05, 2007 2:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
| Dust bunnies in the enterprise should be clearly marked "Here be dragons". |
Fire breathing dust bunnies? I like it! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Jun 05, 2007 1:35 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I was often a big fan of upgrading just to upgrade. What harm can it do, right?
Then one month I started upgrading from CSD6 / CSD7 to CSD8.
An upgrade can cause a lot of harm. Makes the decision to upgrade something that is working just fine a little more complicated.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jun 05, 2007 4:23 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Making the decision never to upgrade something because it might be problematic is always the wrong choice. And sometimes it's not always clear that making the decision to upgrade something "later" is the same as making the decision to upgrade something "never".
Making the decision to upgrade something SLOWLY AND CAREFULLY, rather than as a matter of course.... is fine.
But, again, anything that needs to be handled that carefully is probably a lot more critical to the business than it appears at first glance... and so should get more than just a SECOND glance.... at least a piercing stare.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jun 06, 2007 9:35 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I wish there was an easy for the MQAdmin to look at a client connection and tell what version the originating client is.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
