| Author |
Message
|
| Trainee |
 Posted: Wed Dec 27, 2006 3:46 pm Post subject: Fix13 for MQ5.3 |
 |
|
Centurion
Joined: 27 Oct 2006
Posts: 124
|
Hi ,
we have
MQ 5.3 with csd 11 and
mqsi 2.1 with csd 8
we are going to apply csd 13 which has fix for DST 20007 on WMQ 5.3
Any one does know that will create a compatability problem after applying fix 13 on WMQ5.3 with mqsi2.1.
Thank you
Trainee |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Dec 27, 2006 4:44 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Applying CSD 13 of MQSI 2.1 is a complete waste of your time.
You should, instead, migrate all of your code to 6.0.2 of WMB.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jsware |
| Posted: Thu Dec 28, 2006 4:50 am Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
| jefflowrey wrote: |
Applying CSD 13 of MQSI 2.1 is a complete waste of your time.
You should, instead, migrate all of your code to 6.0.2 of WMB. |
I think (s)he want's to apply CSD13 to MQ, not integrator.
Considering how old 2.1 is and went out of service quite a while back, I doubt whether anybody else has tried it. Let us know how you get on as you'll be our guinea pig 
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 28, 2006 5:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
AFAIK last CSD for MQSI 2.1 was CSD 9. I didn't even know there was a CSD 13 for 5.3 - thought it stopped at 12.
It's my day for learning things. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pathipati |
| Posted: Thu Dec 28, 2006 5:10 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| I guess Trainee is talking about CSD 13 for MQ 5.3 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 28, 2006 5:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I guess so. 
There have never, that I know of, been any compatibility problems with CSD/FP/RP/etc levels of MQ and levels of WMB.
It's still usually a waste of time to apply maintenance to an environment that should instead be obsolesced, unless there are specific fixes to bugs that are actually being encountered.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| pathipati |
| Posted: Thu Dec 28, 2006 5:18 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
I agree.
But Trainee is looking for DST 20007 fix on WMQ 5.3 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 28, 2006 5:25 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
There is NO DST fix for WMQI 2.1, though, so again... no real value.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Trainee |
| Posted: Thu Dec 28, 2006 9:47 am Post subject: Thanks for Replies |
|
|
Centurion
Joined: 27 Oct 2006
Posts: 124
|
Actually we have very few message flows in wmqi2.1 so we planned to migrate them at the end of january.
Before that we are applying fix13 to WMQ5.3, we are thinking that will raise any compatable issues with mqsi2.1( I guess if we migrate before march there is no need to apply DST fix i.e 13 for WMQ5.3)
Regarding MB6 I found the following information
1)For Message Broker V6.0:-
Fix 2 and 3 has updates to reflect the changes in US Daylight Savings Time that are occurring in 2007
2)For Toolkit V6.0
USERS AFFECTED: Users of WebSphere Message Broker V6.0 Toolkit using named MRM Time zones. If the ESQL has this data for interactions between the TIMESTAMP, GMTTIMESTAMP, TIME or GMTTIME types.
FIX: APAR number IC49246, mb6002_ifix006.zip
3)JVM:
Update to internal JVM required for the American DST changes in 2007.
An update is required to the embedded Java JRE within WebSphere Message Brokers to change the Java time zone information.
Fix: APAR number IY87782
Question: If I apply the fix 3 to MB6 do I need to apply patch for JVM also.
If I don't apply patch for Toolkit I can use it for administration purpose successfully not for the developmet?
We already applied fix 3 to MB 6
I appreciate your time
Thank you
Trainee |
|
| Back to top |
|
|
| pathipati |
| Posted: Thu Dec 28, 2006 10:04 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| Actually now you will find MB 6.0.2 with interimfix 1, so again it's waste of time to go with 6.0.1.3. |
|
| Back to top |
|
|
| Trainee |
| Posted: Thu Dec 28, 2006 11:02 am Post subject: embedded Java JRE within WebSphere Message Brokers |
|
|
Centurion
Joined: 27 Oct 2006
Posts: 124
|
I have MB 6.0.0.3
My question is do I need to apply patch for JVM also even after fix 3
beacuse in IBM site it is saying like this
An update is required to the embedded Java JRE within WebSphere Message Brokers to change the Java time zone information
Thank you
Trainee |
|
| Back to top |
|
|
| pathipati |
| Posted: Thu Dec 28, 2006 11:14 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| Not sure, Can you post that link here.. |
|
| Back to top |
|
|
| jsware |
| Posted: Thu Dec 28, 2006 11:56 pm Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
| pathipati wrote: |
| Actually now you will find MB 6.0.2 with interimfix 1, so again it's waste of time to go with 6.0.1.3. |
At the risk of stiring up a heated discussion, I don't always agree that its best to go with the latest and greatest of versions.
* Sometimes, the latest versions have not been tested by enough bleeding edge installers to discover newly introduced bugs. Remember the WMQ5.3 CSD08-11 issues with Java/client connections etc. etc.
* I would hope that you would have tested your software against a particular version/fixpak combination and, if found to be OK, would start rolling that out across production. I wouldn't be happy going with the latest fixpak without testing it first.
* IMHO there is an element of if it ain't broke don't fix it in not applying the latest fixpak. Don't roll out fixpaks unless you need to.
If however you are starting to upgrade your estate, then by all means choose the latest version and a fixpak level to test your applications against.
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Dec 29, 2006 12:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| scottj2512 wrote: |
| I don't always agree that its best to go with the latest and greatest of versions. |
It certainly depends on where you are in the cycle; if you're starting out use the latest, if you have a working software estate then stick with it. The flip side of this is of course judging how far behind the bleeding edge you want to be; the "if it ain't broke" mentality leads to MQSI 2.1 persisting far longer than it should have. Especially when it's a management mentality.
Testing a particular combination is vital - it's worrying how often two things which are perfectly fine exhibit odd effects when used together.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| pathipati |
| Posted: Fri Dec 29, 2006 5:29 am Post subject: |
|
|
Master
Joined: 03 Mar 2006
Posts: 296
|
| Quote: |
| It certainly depends on where you are in the cycle |
I agree with Vitor. |
|
| Back to top |
|
|
|
|
