In an environment that includes HP,
Solaris and z/OS servers (in many cases at current CSD levels) we have had
problems with auto-defined cluster sender channels going into a retry state
… after a server is upgraded to v5.3. Removing queue managers from the cluster
and adding them back after upgrade is completed has been a reasonable
work-around in our environment where the number of clustered queue managers is
limited. Circuitous, but it works.
-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED]
On Behalf Of Kenneth M Viney
Sent: Thursday, September 04, 2003 9:21 PM
To: [EMAIL PROTECTED]
Subject: Seeking advice/comments
on upgrading from v5.2 to v5.3
Hi all
Currently
my site is using MQSeries v5.2 on both a distributed ( Windows NT) and MVS
Mainframe. With the LAN side of things we have not implemented any CSDs
associated with v5.2 due to all sorts of reasons - including the fact that
there never seemed to be a window of opportunity to interrupt development and
QA work to upgrade. But now I am strongly suggesting that our site
"bites the bullet" and moves to v5.3 along with the associated CSD04.
Currently we are upgrading our Desktops to Windows XP (which means that the
Administrators who may have MQ Server installed on their Desktops will have to
remain as NT until v5.3 is installed. Soon within a few months the LAN
will be moved to a Windows 2000 environment.
What I
would like to know is ... has anyone had any sort of major problems or hiccups
with moving from v5.2 to v5.3 ? Any hints, tips or advice I should be
aware of when upgrading?
I
would appreciate any comments or feedback regarding this issue.
Ken
Viney
DMR
Consulting
61 3
9664 6626
This message and any attachments are confidential and for the addressee only.
It may be subject to legal privilege or confidentiality obligations
imposed by legislation. If you have received it in error, please notify
the sender and immediately delete the message without making any copy of it.
The legal effect of this message is subject to its compliance with our
Electronic Communication Policy and Guidelines (available at
http://www.tac.vic.gov.au/ecom-policy and at
http://www.taclaw.com.au/taclawecom-policy). You should consider whether
this message includes a digital signature, and whether it complies with those
guidelines, when deciding whether it should be relied upon.
It is the policy of TAC and TAC Law that our e-mail addresses are for business
use only. All e-mail sent to us may be inspected and used for any lawful
purpose. Our policy prohibiting transmission of inappropriate material via
e-mail is strictly enforced.
|
