| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ servers upgrade to V8.0 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ashok_Athipatla |
 Posted: Fri Nov 14, 2014 12:25 pm Post subject: MQ servers upgrade to V8.0 |
 |
|
Newbie
Joined: 19 May 2014
Posts: 1
|
| Currently we are using MQ V7.0 in Linux and Z/OS servers. We have more than 70 MQ clients who are using these MQ servers. We are planning to upgrade our servers to latest versions as End of support for V7.0 is Sep 2015. We are still checking whether to go to V8.0 or V7.5. Please suggest whether V8.0 is good option. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Nov 14, 2014 12:44 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
v7.5 has additional security features on top of v7.0 - depending on exactly which release of v7.0 you're running on.
V8 has additional security features on top of v7.5.
So it may be "easier" to migrate to v7.5 and then plan to migrate to v8 next year.
But it may be less effort over all to migrate to v8 - provided you spend more time up front experimenting with the security features. |
|
| Back to top |
|
|
| cicsprog |
| Posted: Wed Mar 11, 2015 9:28 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
fyi
Migrating the mainframe MQMs you can't skip releases. You will need to migrate the mainframe from 7.0 to 7.1.0 to 8.0. |
|
| Back to top |
|
|
| dogbert64 |
| Posted: Thu Mar 26, 2015 1:23 pm Post subject: |
|
|
Acolyte
Joined: 11 Jun 2003
Posts: 58
|
Migrating the mainframe MQMs you can't skip releases. You will need to migrate the mainframe from 7.0 to 7.1.0 to 8.0
Are you sure about that?
This link talks about going from v7.0.1 OR v7.1 to v8.0, and falling back.
http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.mig.doc/q122870_.htm
Migration support is provided from both WebSphere MQ version 7.0.1 and WebSphere MQ version 7.1.0 to IBM MQ for z/OS version 8.0.0.
Assuming he is at 7.0.1 on z/OS, (and not 7.0, which IIRC was pulled shortly after release), then with the proper PTFS he could jump straight to v8.0. If he is actually at v7.0, then your statement is correct (unless there is an IBM document which says you can go from v7.0 as well to v8.0....you never know with IBM). |
|
| Back to top |
|
|
| cicsprog |
| Posted: Fri Mar 27, 2015 9:23 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 27, 2015 9:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
This is IBM CYA. They say you should move to v7.1 first in Prod.
A few sentances down they say it's more appropriate to go from v7.0 -> v8.0 if you take backups first. I'm not sure who exactly would do any kind of migration without taking backups first, but there's bound to be one and IBM are accounting for that, and the demands of IBM's legal department.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| dogbert64 |
| Posted: Fri Mar 27, 2015 10:09 am Post subject: |
|
|
Acolyte
Joined: 11 Jun 2003
Posts: 58
|
Reread the second sentence again, closely, and look at the section it is in.
For production systems you should, firstly, migrate the unsupported release of IBM® MQ to WebSphere® MQ version 7.1, following the instructions given in the documentation for that release.
The keyword is unsupported. It is saying that if you are at an unsupported release, then you should first go to v7.1, and then to v8.0. But v7.0.1 is also a supported release (at least until Sep 30, 2015). So the way I read this is that IBM is recommending to go from "unsupported release" --> v7.1 --> v8.0 than to go from "unsupported release" --> v7.0.1 --> v8.0. And that makes sense to me. But if someone wanted to choose the second path, then that would work as well (at least until Sep 30, 2015 - after that, don't count on support from IBM).
The link I provided specifically states you can fall back from v8.0 to v7.0.1. So if I was to believe that you MUST upgrade to v8.0 ONLY from v7.1, then why deliver fallback to v7.0.1 from v8.0?
Also, why would IBM provide a PTF (circa Nov 2014) to support something that cannot be done (to fallback to v7.0.1 after an upgrade to v8.0)?
http://www-01.ibm.com/support/docview.wss?uid=swg1PI19721&myns=swgws&mynp=OCSSFKSJ&mync=E
PI19721: BACKWARDS MIGRATION FROM V8 AND COEXISTENCE WITH V8
Allow V701 or V710 queue-manager backwards migration from V8,
and coexistence with a V8 queue-manager in a queue-sharing
group.
.
Additional keywords:
MQ0800C/K toleration
Local fix
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
* Release 0 Modification 1 and Version 7 *
* Release 1 Modification 0 *
****************************************************************
* PROBLEM DESCRIPTION: Enable backward migration to version *
* 7.0.1 after a queue manager has been *
* started with the version 8.0.0 code. *
* *
* Enable backward migration to version *
* 7.1.0 after a queue manager has been *
* started with the version 8.0.0 code. *
* *
* Enable version 7.0.1 queue managers to *
* co-exist in a queue sharing group with *
* version 8.0.0 queue managers. *
* *
* Enable version 7.1.0 queue managers to *
* co-exist in a queue sharing group with *
* version 8.0.0 queue managers. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
PTFs for the backward migration APAR must be applied on version
7 queue managers prior to attempting fallback from IBM MQ for
z/OS version 8.0.0.
Version specific notes follow:
When reverting to Version 7.0.1 after running a queue manager at
version 8.0.0 the following should be considered: |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Mar 27, 2015 10:27 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
For most IBM products - z/OS and midrange, there are several v/r/m's that are supported for both co-existence and migration.
"Supported" means that it will work - with support if you need it. "Unsupported" does NOT mean that it won't work, only that you might be without support should you need it.
Long ago, I gave up being annoyed by having to install a hop or two software to get current. I've moved on to being annoyed by other things.
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
