| Author |
Message
|
| drummerboyuk |
 Posted: Wed Feb 08, 2012 2:26 am Post subject: 200 and 500 class interface indefinitions in MQAX200.DLL? |
 |
|
Newbie
Joined: 08 Feb 2012
Posts: 7
|
Hi,
I was interested in knowing what the difference was between the 200 and 500 class interface definitions in the MQAX200.DLL? e.g. IMQMessage500 and IMQMessage200? Which one should be used? Do they all support/work on all platforms? I am having problems with MQ COM+ code that worked on a Windows 2003 server R2 (32 bit) and now no longer works on a Windows 2008 server R2 (64bit). I will post details of the error in another post.
I am new to MQ Websphere so apologies for my lack of knowledge.
Thanks for your help and advice.
Stef |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Feb 08, 2012 2:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You shouldn't be using this API in any modern application.
You should be using the .NET MQ API.
I probably used to know the difference between the 200 and 500 class interfaces, but I have entirely forgotten, as it's been at least 6 years since anyone I know of has done anything meaningful with this API.
If you're really still curious about this distinction, it is probably somewhere in the documentation.
But again, please stop using this API immediately and start using the .NET API. There's no guarantee that you will get any kind of 64-bit support for the COM+ API, and I strongly suspect you will have difficulties raising PMRs against it. |
|
| Back to top |
|
|
| drummerboyuk |
| Posted: Wed Feb 08, 2012 3:17 am Post subject: |
|
|
Newbie
Joined: 08 Feb 2012
Posts: 7
|
Hi,
Thanks for your reply.
Unfortunately I am using Delphi (XE2) as the development language and not .NET. And yes as you have guessed this is not a modern application. 
What API should I be now using with Delphi (XE2)? Obviously if possible I do not want to have to totally have to re-develop the suite of MQ COM+ components.
Thanks
Stef |
|
| Back to top |
|
|
| JasonE |
| Posted: Wed Feb 08, 2012 4:06 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
As Jeff said, the COM interface is stabalized... that means it should carry on working and is supported in so far as the functionality it provides.
Java/JMS, C, .NET, XMS etc are the main supported and continually extended interfaces. A google implies Delphi can call .net code (e.g. http://www.drbob42.com/examines/examin36.htm) but since I have never seen nor used it, I might be talking complete garbage here! |
|
| Back to top |
|
|
| drummerboyuk |
| Posted: Tue Feb 28, 2012 9:55 am Post subject: |
|
|
Newbie
Joined: 08 Feb 2012
Posts: 7
|
Hi,
Thanks for that info.
It might be worth then trying to interface with the .NET MQ API then in the Delphi COM+ dll. Do you know if there is a 64 bit version of this .NET MQ API? I would quite like to move away from running 32 bit code (COM+) on a Windows 2008 64 bit server and I think the only thing currently stopping us is the legacy 32bit MQ driver (MQAX200.DLL).
Thanks
Stef |
|
| Back to top |
|
|
| JasonE |
| Posted: Tue Feb 28, 2012 10:08 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| I think the .net code is built as 'any' rather than any more specific cpu so should just work. I have a feeling that if you want to use bindings (going through client or server native code, rather than fully managed) then you'll need to use v7+ as thats when 64 bit API calls were supported I think |
|
| Back to top |
|
|
|
|
