| Author |
Message
|
| fedux |
 Posted: Mon Feb 05, 2007 12:26 pm Post subject: MQ 6.0 / 5.3 |
 |
|
Novice
Joined: 12 Jan 2007
Posts: 20
|
Hi.
I want to know if exists any incompatibility between MQ5.3 and MQ6.0 |
|
| Back to top |
|
 |
| csmith28 |
| Posted: Mon Feb 05, 2007 12:48 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
If you are talking about WMQ5.3 MQManagers exchanging messages with WMQ6.0 MQManagers, then no, I am not aware of any compatibility issues of that nature.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 06, 2007 12:47 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Only the new clustering parameters. If you've set the new v6 clustering parameters to something other than defaults (which cause the v5.3 behaviour) then the v5.3 managers will not honour the changes. This can result in messages being distributed in ways you don't expect.
Cluster still works though.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Tue Feb 06, 2007 1:53 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
You should apply the relevant patches - otherwise MQ may not work as you expect ...
_________________
Regards
Hubert |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Feb 06, 2007 4:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Read up as well on JMS client.
There are some minor changes like you can no longer use the qcf.createConnection() when using a stand alone JMS client but should use the qcf.createConnection(user,pwd) form when using stand alone client JMS...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| fedux |
| Posted: Tue Feb 06, 2007 6:13 am Post subject: |
|
|
Novice
Joined: 12 Jan 2007
Posts: 20
|
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Feb 06, 2007 6:52 am Post subject: |
|
|
Guest
|
| Refer to SC34-6604-01 WebSphere MQ Migration Information fordetails. |
|
| Back to top |
|
|
| dixanms |
| Posted: Wed Oct 03, 2007 4:40 pm Post subject: |
|
|
Newbie
Joined: 03 Oct 2007
Posts: 6
|
For the specific case of having clusters setup is section "Migrating a queue manager cluster" from document "SC34-6604-01 WebSphere MQ Migration Information" (see below).
Nevertheless, reading this I'm in doubt about 2 cases:
1. Is it correct to make participate a new v6.0 qmgr not repository in a cluster hold by an existing v5.3 full repository qmgr? Specifically, the former will run on AIX 5.3 and the later runs on zOS. It seems it is ok to do that if you are not going to use the new v6.0 cluster parameters, but it's not pretty clear.
2. What if creating a new cluster between that pair of qmgrs? I'm having problems getting a cluster queue locally defined in my v5.3 zOS qmgr to be seen in the AIX qmgr, but the other way is not a problem: i.e. to have a cluster queue locally defined in my v6.0 qmgr to be seen in the zOS qmgr.
Can anyone clarify this?
---------------------- Migrating a queue manager cluster -----------
This section gives information about migrating queue manager clusters to
WebSphere MQ Version 6.0.
Migrate the repository queue managers (that is, those queue managers holding a
full repository) first, before migrating the other queue managers.
WebSphere MQ Version 6.0 introduces new workload balancing attributes on
queues, queue managers, and channels. See Chapter 12 of WebSphere MQ Queue
Manager Clusters for full details of these attributes. If these parameters are left at
their default values, the queue managers will behave as they did before migration.
Use of the new workload balancing parameters in a cluster containing a mixture of
Version 5.3 and Version 6.0 queue managers will give unpredictable results.
[/i]
_________________
Dixan Martinez
Systems Administrator |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Oct 03, 2007 10:47 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| dixanms wrote: |
| It seems it is ok to do that if you are not going to use the new v6.0 cluster parameters, but it's not pretty clear. |
It's exactly as laid out in the documentation snippet you quote. So long as the new parameters are left to their default values it'll be fine. If they're not, it's unpredictable. Seems clear enough.
| dixanms wrote: |
| I'm having problems getting a cluster queue locally defined in my v5.3 zOS qmgr to be seen in the AIX qmgr, but the other way is not a problem: i.e. to have a cluster queue locally defined in my v6.0 qmgr to be seen in the zOS qmgr. |
Again, the snippet you quote says "Migrate the repository queue managers (that is, those queue managers holding a
full repository) first, before migrating the other queue managers". You say that the v5.3 is a full repository manager, and the other is a v6?. Still seems clear enough.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| dixanms |
| Posted: Wed Oct 03, 2007 11:58 pm Post subject: |
|
|
Newbie
Joined: 03 Oct 2007
Posts: 6
|
Vitor, thanks for your reply.
My case is:
* I CAN NOT migrate my zOS v5.3 full rep qmgr to v6 for some reasons yet.
* I need to install a new qmgr using current v6 on AIX 5.3
* I need to make participate this new v6 qmgr in an existing cluster hold by my zOS v5.3 full rep qmgr
If it's required "to migrate first the v5.3 full rep qmgrs (to v6)" to be able to have the existing cluster working with my new v6 qmgr, then the answer for my 1st question is NO, no matter if we keep the default cluster parameters in the new v6.0 qmgr.
Is it still clear for you or am I missing something???
_________________
Dixan Martinez
Systems Administrator |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 04, 2007 12:28 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Ok, to pound it out flat:
- it's perfectably acceptable to mix v5.3 & v6 queue managers in a cluster provided that the new parameters are not used;
- it's recommended (and I'm prepared to be told mandatory by someone who knows better) that the FRs are migrated to v6 before the PRs. Your experience seems to indicate it causes problems.
Sounds like you need to explore other, interim options. Depending on what your clusters used for there are a couple of possibilities.
Enjoy
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bbburson |
| Posted: Thu Oct 04, 2007 5:40 am Post subject: |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
| dixanms wrote: |
| I'm having problems getting a cluster queue locally defined in my v5.3 zOS qmgr to be seen in the AIX qmgr, . . . |
Remember, if the AIX qmgr is a partial repository it will not see clustered queues until it needs them. Try putting to a zOS clustered queue from AIX and see if it shows up then. |
|
| Back to top |
|
|
| dixanms |
| Posted: Thu Oct 04, 2007 1:32 pm Post subject: |
|
|
Newbie
Joined: 03 Oct 2007
Posts: 6
|
Thanks Bruce for replying
| bbburson wrote: |
| Remember, if the AIX qmgr is a partial repository it will not see clustered queues until it needs them. Try putting to a zOS clustered queue from AIX and see if it shows up then. |
Actually we already made that test which resulted
in error 2085 (MQRC_UNKNOWN_OBJECT_NAME) :|
_________________
Dixan Martinez
Systems Administrator |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Oct 04, 2007 1:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Did you check the cluster attribute and cluster namelist attribute of the queue on zOS? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Oct 04, 2007 3:58 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Migrating WebSphere MQ queue manager clusters to WebSphere MQ V6
http://www.ibm.com/developerworks/websphere/library/techarticles/0605_vanstone/0605_vanstone.html
We had 5.3 and 6.0 QMs in the same cluster for months with no problems. However, we upgraded the FRs repositories first.
In the above link Ian specifically talks about your dilema. You should be OK.
You say you can't upgrade the FRs? You probably could if you pushed back hard enough. 
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
