| Author |
Message
|
| scraigMQS |
 Posted: Fri Dec 22, 2006 7:17 pm Post subject: MQCONN Errors |
 |
|
Newbie
Joined: 22 Dec 2006
Posts: 1
|
I'm trying to deploy an older version of the MQSeries Client (5.1 for NT) to a Windows 2000 workstation. I continue to get MQCONN errors and have tried it every way I can think of. I'm wondering if it is worth the effort. The project is a temporary fix for the issue of an unreliable NT workstation.
I believe I'm getting these errors because compatibility issues - you need to upgrade to at least 5.2 to run it on Win2000. The procedure calls in the script seem "old school" and are preventing the application from running properly in the 2000 environment.
Can anyone confirm this? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Dec 27, 2006 12:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Using ANY 5.1 code is not worth the effort! It's as old as the hills. I'm interested but not surprised to discover it's incompatible with newer versions (though I hesitate to describe 5.2 as "new" - it's out of support and likewise a waste of effort) - the client code is fairly stable & is relaxed about what it connects to.
Download the new client. And don't use 5.2 for the queue manager; you should be on 5.3 at least! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Dec 27, 2006 6:06 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Here is a link to find what is supported for which dates.
http://www-306.ibm.com/software/info/supportlifecycle/
Very handy when talking to manager types...
Even WebSphere MQ 5.3 will expire Sep 2007.
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| jsware |
| Posted: Wed Dec 27, 2006 6:31 am Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
| JosephGramig wrote: |
| Even WebSphere MQ 5.3 will expire Sep 2007. |
That and WebSphere Business Integrator Message Broker 5.0 expires Sep 2007. I'm not looking forward to upgrading our MQ and message broker estate in 2007 
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 27, 2006 6:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| scottj2512 wrote: |
| I'm not looking forward to upgrading our MQ and message broker estate in 2007 |
You think you've got trouble? Q1 we're moving production off MQ5.2 and MQSI 2.1.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| tleichen |
| Posted: Thu Dec 28, 2006 7:47 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
| Vitor wrote: |
Using ANY 5.1 code is not worth the effort! It's as old as the hills. I'm interested but not surprised to discover it's incompatible with newer versions (though I hesitate to describe 5.2 as "new" - it's out of support and likewise a waste of effort) - the client code is fairly stable & is relaxed about what it connects to.
Download the new client. And don't use 5.2 for the queue manager; you should be on 5.3 at least! |
I agree with Vitor. Since you are creating a new environment anyway, why not 5.3? Or better yet, 6.0.2? or 6.1? 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
|
|
