| Author |
Message
|
| tapak |
 Posted: Tue Dec 06, 2005 11:42 am Post subject: Does As/400 can have MQ Clients |
 |
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
I got confused with the below statement in the MQSeries Client document. As per my knowledge all the platforms which support Java should be able to connect to MQServer using MQAPI for Java or JMS. Please correct me if I am wrong.
MQSeries clients on other platforms
Most MQSeries products supply files for clients on the same platform as the server
and for clients on other platforms. The following MQSeries products supply files
for clients on other platforms only:
v MQSeries for AS/400
v MQSeries for MVS/ESA
v MQSeries for OS/390
v MQSeries for Tandem NSK
v MQSeries for VSE/ESA
_________________
IBM Certified Solution Designer -- WebSphere MQ V5.3
IBM Certified Solution Designer -- WebSphere Business Integration - Message Broker V5
IBM Certified Specialist -- IBM WebSphere App Svr Advd Single Svr Ed. for Multiplatforms (Java) |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Dec 06, 2005 11:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Any platform that runs Java can run the plain WebSphere MQ API for Java in client mode, if you copy the right jar files to the machine.
IBM supplies regular MQ Client distributions, which include not only the Java APIs but also the native libraries for the C/C++ API and etc.
There is an IBM MQ client distribution for AS/400, last I knew. And that quote seems to imply it.
IBM does not supply a standalone installer for the Java API. You have to manually move the right jar files from a supported client or server installation to the machine you want to use Java on - if that machine does not have a client distribution.
IBM will not support the client on platforms that do not have IBM supplied Distributions.
Willow Technologies has the license from IBM to produce ports of MQ on platforms that IBM will not support. Willow Technologies supports those platforms that it supplies clients and servers for.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Dec 06, 2005 6:15 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| There is an IBM MQ client distribution for AS/400 |
I think you mean, "there is not a client for as/400". (outside of the java client)
_________________
-wayne |
|
| Back to top |
|
|
| tapak |
| Posted: Mon Dec 12, 2005 11:30 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2005
Posts: 149
Location: Hartford,CT
|
Jeff ,Thank you for the input . Even the Xtended Transaction Client is not supported on MQSeries on OS/400 platform .Does that mean applications deployed on WAS on OS/400 cannot have 2 phase commit ,unless the MQ Series Server is installed on the same machine .
| jefflowrey wrote: |
Any platform that runs Java can run the plain WebSphere MQ API for Java in client mode, if you copy the right jar files to the machine.
IBM supplies regular MQ Client distributions, which include not only the Java APIs but also the native libraries for the C/C++ API and etc.
There is an IBM MQ client distribution for AS/400, last I knew. And that quote seems to imply it.
IBM does not supply a standalone installer for the Java API. You have to manually move the right jar files from a supported client or server installation to the machine you want to use Java on - if that machine does not have a client distribution.
IBM will not support the client on platforms that do not have IBM supplied Distributions.
Willow Technologies has the license from IBM to produce ports of MQ on platforms that IBM will not support. Willow Technologies supports those platforms that it supplies clients and servers for. |
_________________
IBM Certified Solution Designer -- WebSphere MQ V5.3
IBM Certified Solution Designer -- WebSphere Business Integration - Message Broker V5
IBM Certified Specialist -- IBM WebSphere App Svr Advd Single Svr Ed. for Multiplatforms (Java) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Dec 12, 2005 11:32 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| wschutz wrote: |
| Quote: |
| There is an IBM MQ client distribution for AS/400 |
I think you mean, "there is not a client for as/400". (outside of the java client) |
I read the quote wrong.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Dec 12, 2005 9:49 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| jefflowrey wrote: |
Any platform that runs Java can run the plain WebSphere MQ API for Java in client mode, if you copy the right jar files to the machine.
|
With v5.3 the above statement is not true for z/OS.
You can run your java program in bindings mode only on z/OS. That might have changed with MQ v6. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Dec 13, 2005 4:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| vennela wrote: |
| jefflowrey wrote: |
Any platform that runs Java can run the plain WebSphere MQ API for Java in client mode, if you copy the right jar files to the machine.
|
With v5.3 the above statement is not true for z/OS.
You can run your java program in bindings mode only on z/OS. That might have changed with MQ v6. |
Really? If I copy the jar file from a distributed platform, and ensure that the USS user has access to the TCP/IP interface, then still I can't establish an outbound client connection using Java?
Wow.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Dec 13, 2005 9:20 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
AFAIK, you don't have to copy the jar files also. IBM will supply the jars for MQ on z/OS.
As soon as you try to create the QMGR object by setting the MQEnvironment property, it fails with 2012 or something and I don't remember exactly.
Also from the manual
| Quote: |
| Miscellaneous differences with z/OS and OS/390 |
| Quote: |
| MQQueueManager constructor Client connect is not supported on z/OS and OS/390. Attempting to connect with client options results in an MQException with MQCC_FAILED and MQRC_ENVIRONMENT_ERROR. The MQQueueManager constructor might also fail with MQRC_CHAR_CONVERSION_ERROR (if it fails to initialize conversion between the IBM-1047 and ISO8859-1 code pages), or MQRC_UCS2_CONVERSION_ERROR (if it fails to initialize conversion between the queue manager’s code page and Unicode). If your application fails with one of these reason codes, ensure that the National Language Resources component of Language Environment® is installed, and ensure that the correct conversion tables are available. |
|
|
| Back to top |
|
|
|
|
