Hi Steven,

WMQ 6.0 clients should be able to communicate with WMQ 5.3 servers. Just
link your app code against the 6.0 MQ API library (mqic32.lib), and deploy
to your client (where the V6.0 client must be installed in order for this to
work of course).

Another alternative for .NET client code (if you wish to pursue this) is to
use the IBM Message Service clients. There are versions of this for C/C++
and .NET. Currently the .NET client code is in beta, but it has been well
tested, and is being investigated by several customers already. The C/C++
client is currently a category 2 (as-is) SupportPac.

The URL is http://www-1.ibm.com/support/docview...id=swg24007092 -
follow the link from here to the beta site for the .NET clients.

Regards,
Martin


wrote in message
news:423066849.1133207671054.JavaMail.wassrvr@ltsg was007.sby.ibm.com...
>I have an application wrote in C# .NET 1.1 which I know 5.3 does not
>support. My question is can I use the 6.0 Client to communicate with the
>5.3 Server and if so where may I find whitepapers or FAQs on this subject?
>
> Or is the answer I must be using a 6.0 Server?

>>I have an application wrote in C# .NET 1.1 which I know 5.3 does not
>>support.

It's not true MQ 5.3 doesn't work with C#.

Since MQ5.3 CSD05 on Windows, IBM has shipped the MQ classes for .NET.
If you grab MQ5.3 CSD10 or whatever is the current latest, you will get
amqmdnet.dll, which is the .NET assembly that provides the APIs for C# (and
VB, and any .NET language) to connect to MQ.

MQ 6.0 also includes the amqmdnet.dll assembly.


On the Message Service Clients from IBM:
I thought the Message Service Clients (I think IBM calls them "XMS"
clients ) were essentially JMS protocol implementations on .NET / C++. In
other words, when you send a JMS message, you are implicitly invisibly
adding formatting and envelope gunk (RFH2) around the message payload. The
result is a non-JMS app (like .NET or C++) cannot unwrap the message
payload. In other words JMS works not only as a message system API, but
also drags in a message envelope and formatting "standard." The XMS stuff
allows you to read and write "JMS" messages from systems that are nont Java
or do not support the full JMS API. So I don't know that these things are
valuable, unless you need to specifically interconnect non-JMS systems with
JMS systems.

in summary, I think If you want to send a message from .NET to .NET via MQ,
then you don't need XMS. Or from .NET to CICS, or .NET to AS400/RPG, or ...
etc.


-D




"Martin G" wrote in message
news:dmfs6f$amiq$1@news.boulder.ibm.com...
> Hi Steven,
>
> WMQ 6.0 clients should be able to communicate with WMQ 5.3 servers. Just
> link your app code against the 6.0 MQ API library (mqic32.lib), and deploy
> to your client (where the V6.0 client must be installed in order for this
> to work of course).
>
> Another alternative for .NET client code (if you wish to pursue this) is
> to use the IBM Message Service clients. There are versions of this for
> C/C++ and .NET. Currently the .NET client code is in beta, but it has
> been well tested, and is being investigated by several customers already.
> The C/C++ client is currently a category 2 (as-is) SupportPac.
>
> The URL is
> http://www-1.ibm.com/support/docview...id=swg24007092 - follow
> the link from here to the beta site for the .NET clients.
>
> Regards,
> Martin
>
>
> wrote in message
> news:423066849.1133207671054.JavaMail.wassrvr@ltsg was007.sby.ibm.com...
>>I have an application wrote in C# .NET 1.1 which I know 5.3 does not
>>support. My question is can I use the 6.0 Client to communicate with the
>>5.3 Server and if so where may I find whitepapers or FAQs on this subject?
>>
>> Or is the answer I must be using a 6.0 Server?
>
>