| Author |
Message
|
| andy840920 |
 Posted: Sun May 20, 2007 5:54 am Post subject: must install MQ client ? |
 |
|
Apprentice
Joined: 29 Apr 2007
Posts: 44
|
| my program use MQCONNX connect to MQ server QMGR and execute MQPUT or MQGET operation. must i install the MQ Client program? because is not should install client by Java. only use some jar packages. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun May 20, 2007 8:09 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You can of course only install the java jars (this will carry some restrictions).
But to get the full benefit (including translation of CCSID for text messages) you should install the full MQ Client and always reference the jars from the client install path...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun May 20, 2007 12:01 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Also the only client configuration supported by IBM is the one where the client is fully installed. Hence if you feel you'll need PMR support at some point in the future (e.g. a production setup) you're best advised to install the client.
It's not like the license costs you anything..... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| andy840920 |
| Posted: Mon May 21, 2007 3:06 am Post subject: |
|
|
Apprentice
Joined: 29 Apr 2007
Posts: 44
|
| fjb_saper wrote: |
You can of course only install the java jars (this will carry some restrictions).
But to get the full benefit (including translation of CCSID for text messages) you should install the full MQ Client and always reference the jars from the client install path...
Enjoy |
but my program writed by C language must install the client? my program linked libmqic.so and running on linux as3 and is not install the client. use MQCONNX function and directly MQCD fields like connectName... but MQOPEN ended with 2018, the MQCONNX is successful. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon May 21, 2007 5:47 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| andy840920 wrote: |
| fjb_saper wrote: |
You can of course only install the java jars (this will carry some restrictions).
But to get the full benefit (including translation of CCSID for text messages) you should install the full MQ Client and always reference the jars from the client install path...
Enjoy |
but my program writed by C language must install the client? my program linked libmqic.so and running on linux as3 and is not install the client. use MQCONNX function and directly MQCD fields like connectName... but MQOPEN ended with 2018, the MQCONNX is successful. |
AFAIK the C libraries you've linked call the functions installed as part of the client. It's only Java that uses jar files (obviously enough)
Given that 2018 is "HConn error" I don't think the connx worked entirely successfully.....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| andy840920 |
| Posted: Mon May 21, 2007 6:26 am Post subject: |
|
|
Apprentice
Joined: 29 Apr 2007
Posts: 44
|
| Vitor wrote: |
| andy840920 wrote: |
| fjb_saper wrote: |
You can of course only install the java jars (this will carry some restrictions).
But to get the full benefit (including translation of CCSID for text messages) you should install the full MQ Client and always reference the jars from the client install path...
Enjoy |
but my program writed by C language must install the client? my program linked libmqic.so and running on linux as3 and is not install the client. use MQCONNX function and directly MQCD fields like connectName... but MQOPEN ended with 2018, the MQCONNX is successful. |
AFAIK the C libraries you've linked call the functions installed as part of the client. It's only Java that uses jar files (obviously enough)
Given that 2018 is "HConn error" I don't think the connx worked entirely successfully..... |
but i checked CompCode=MQCC_OK and CReason=MQRC_NONE.
by the way
| Quote: |
AMQ9541: CCSID supplied for data conversion not supported.
EXPLANATION:
The program ended because, either the source CCSID '819' or the target
CCSID '1381' is not valid, or is not currently supported.
The 819 CCSID is the Solaris codepage.
The 1381 CCSID is the Windows Simplified Chinese codepage.
|
my mq server installed on windows xp and language enviroment is Simplified Chinese, and create QMGR with CCSID=918, but my mq client and application installed on linux as3. why AMQ9541? if i set CCSID in my program, should execute md.CodedCharSetId = 819? |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon May 21, 2007 6:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If the conn's worked in a C program, and the client's not installed on the application machine, then all that's happened is the conn has failed to detect the lack of the client and thrown a false positive. What the open is trying to tell you is that the conn object is incorrectly formed.
OR....
You have (by some bizarre, inexplicable and unsupported method) established a connection and it's gone out of scope due to a programming bug. Install the client, if the problem persists it's a bug.
As to your other problem, it's better etiquite to start a new thread. Having said that, if I understand you correctly you're setting the CCSID in your source program to the CCSID of the target to force conversion. This is not how it works. Don't set the CCSID yourself, and make sure you've got all the conversion tables you need installed on the target server.
If I've not understood correctly, put a full explaination on a new thread & I'll try again. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
