| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Toolkit and Broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| rknox |
 Posted: Thu Jul 03, 2008 8:15 am Post subject: Toolkit and Broker |
 |
|
Apprentice
Joined: 28 Aug 2007
Posts: 34
|
Is there any reason to require developers to keep a toolkit version in synch with the Broker runtime? I notice the toolkit and broker have completely different fixes but the numbers do seem to correlate, 6.1.0.2 and 6.1.0.1 which would lead me to think they should be in sync.
For example is it necessary to keep the development toolkit at level 6.1.0.1 when the Broker runtime is at 6.1.0.1 or can the toolkit be upgraded to 6.1.0.2, fixpack X without added risk? |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Thu Jul 03, 2008 8:27 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Generally, there is flexibility in the fixpack versions of the toolkit working with fixpack versions of the broker. (There are one or two counterexamples to this in the 6.0 stream, but that's the general rule.)
However, it is a good idea to keep major versions of toolkit and runtime the same; flows developed in a 6.1 toolkit should be destined for a 6.1 broker, for example.
Of course, it's always recommended to keep both toolkit and runtime up-to-date on service. |
|
| Back to top |
|
|
| MrSmith |
| Posted: Thu Jul 03, 2008 8:29 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
We run a completely different toolkit level to that of the runtime and have had no problems on V6 (not V6.1) as there has been a number of reason for the toolkit to have been upgraded due to esql validation errors etc but not had any problems with running the code on an earlier runtime (toolkit is ifix 014 and runtime is CSD5).
I guess to a point it would depend on exactly how far behind you wanted run out of sync as you could never be sure if functionality in either product is not reliant or available in the other without perusing all the APARS fixes etc and therefore cause deployment errors or missed fuctionality. Of course if any such problems exist the support centres first reaction may be for you to sync to the latest pacs for both. |
|
| 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
|
|
|
|
