ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » z/OS WMQ V531 and V6 Co-exist, Refresh Required?

Post new topic  Reply to topic
 z/OS WMQ V531 and V6 Co-exist, Refresh Required? « View previous topic :: View next topic » 
Author Message
bay hoe san
PostPosted: Sat Sep 13, 2008 10:42 pm    Post subject: z/OS WMQ V531 and V6 Co-exist, Refresh Required? Reply with quote

Centurion

Joined: 27 Nov 2006
Posts: 117

Hello,

1. I have 2 full respository qmgrs with V531, 1 residing in LPAR1, the other residing in LPAR2. Assuming there is no change to the other partial repos qmgrs.
Since V531 is already EOS, I need to upgrade both. However, I can only do 1 LPAR at a time. Say, I upgrade 1 of the full repos in LPAR1 to V6, keeping the other full repos in V531 in LPAR2.
2. I have the following queries:
1. Immediately after the upgrade in LPAR1, do I need to do a refresh repos(yes) or repos(no)? Repos with yes or no?
2. Repos in full or partial or all qmgrs?
3. Say, in worst case scenario, a reversion is required in the full repos qmgr in LPAR1 i.e. downgrade to V531, do I need a refresh repos? If required, repos(yes) or repos(no)?
3. I received complains from customer that msgs unable to flow intermittently, so what I did immediately is a repos(yes) in full and everything seem back to normal. Wondering am I right?
4. Pls advise.
5. Thank you.

.Hoe San.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Sun Sep 14, 2008 3:45 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzaj.doc/sc12660_.htm

Were any of these conditions true?
Quote:

It is not normally necessary to issue a REFRESH CLUSTER command except in one of the following circumstances:
Messages have been removed from either the SYSTEM.CLUSTER.COMMAND.QUEUE, or from another queue manager's SYSTEM.CLUSTER.TRANSMIT.QUEUE, where the destination queue is SYSTEM.CLUSTER.COMMAND.QUEUE on the queue manager in question.
Issuing a REFRESH CLUSTER command has been recommended by IBM® Service.
The CLUSRCVR channels were removed from a cluster, or their CONNAMEs were altered on two or more full repository queue managers while they could not communicate.
The same name has been used for a CLUSRCVR channel on more than one queue manager in a cluster, and as a result, messages destined for one of the queue managers have been delivered to another. In this case, the duplicates should be removed, and then a REFRESH CLUSTER command should be issued on the single remaining queue manager that has the CLUSRCVR definition.
RESET CLUSTER ACTION(FORCEREMOVE) was issued in error.
The queue manager has been restarted from an earlier point in time than it last finished, (for example, by restoring backed up data.)



Quote:
Issuing REFRESH CLUSTER does not correct mistakes in cluster definitions, nor is it necessary to issue the command after such mistakes have been corrected.


Regarding Repos YES:
Quote:

This option must not be used if the queue manager is itself a full repository, if it is a full repository, you must first alter it so that it is not a full repository for the cluster in question.



This article may be of interest to you:Migrating WebSphere MQ queue manager clusters to WebSphere MQ V6
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sun Sep 14, 2008 10:46 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

Yes, v531 and v6 can coexist.

Refer to the z/OS WMQ Concepts and Plannaing manual. There is a section on "Migration from previous versions"
_________________
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
View user's profile Send private message
gbaddeley
PostPosted: Sun Sep 14, 2008 8:20 pm    Post subject: Reply with quote

Jedi Knight

Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia

Careful of the terminology. MQ "coexistence" means that two or more versions of MQ can be installed and be run by separate MQ subsystems (queue managers) on the *same* LPAR (or sysplex with shared DASD).

If the two MQ subsystems are running on totally separate LPARs, you probably mean "compatibility" rather than "coexistence".
_________________
Glenn
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sun Sep 14, 2008 9:31 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

You are absolutely correct. MQ v531 and v6 are compatible and they can co-exist. Life is good.
_________________
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
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » z/OS WMQ V531 and V6 Co-exist, Refresh Required?
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.