| Author |
Message
|
| ulasergin |
 Posted: Wed Dec 07, 2005 7:40 am Post subject: CCDIS Not Supported? DO NOT BELIEVE! |
 |
|
Novice
Joined: 05 Apr 2005
Posts: 15
|
I have installed MQ v6 and trying to access it via JMS.
It has been giving the Exception CCSID Not supported exception.
I searched the web and several forums,with lots of suggestions
I have changed numerous setting and none did work!!
BECAUSE: The problem was not related with CCSID.
The server connection channel was specified other than 1414 so the problem was a simple socket connection to the server
BUT MQ misdirected my to CCSID
I wanted to report this here for other people having the same problem wit stupid MQ messages |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed Dec 07, 2005 8:48 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Was this MQ V6 with, or without RP 1?
_________________
-wayne |
|
| Back to top |
|
|
| ulasergin |
| Posted: Thu Dec 08, 2005 1:15 am Post subject: |
|
|
Novice
Joined: 05 Apr 2005
Posts: 15
|
without RP1, my trial to download the fix is rejected,saying that it is restricted to US export laws..
but does this matter?should the error message for not establising a connetion to MQ be 'CCSID not supported' without the fix? I don't think so |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Dec 08, 2005 3:26 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
If this really is a problem, then you should report it to IBM service and open a PMR. Its generally advisable to be up to date on your MQ fixes before caling service (just to make sure that your problem hasn't already been fixed in a RP or FP).
Can you give more info? What platform is this happening on? Are you using the JMS client on the same machine or a different machine than the server? Are you defining the connection using JMSAdmin, in your code or is the channel definition held in a client channel table?
_________________
-wayne |
|
| Back to top |
|
|
| ulasergin |
| Posted: Thu Dec 08, 2005 3:29 am Post subject: |
|
|
Novice
Joined: 05 Apr 2005
Posts: 15
|
| Quote: |
| If this really is a problem |
don't you think such a stupid and misdirecting error message is a problem?
It is on Windows XP platform.Both client and server are on the same machine.The definitions are made by JMSAdmin and MQExplorer |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Dec 08, 2005 3:52 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Well, yes I do think its a problem, which is why I think you should call service and open a PMR so it gets fixed. Since you are interested in saving others the same bad experience that you had, opening a PMR would be the thing to do. Thanks....
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 08, 2005 4:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Also, if this is a JMS Exception, it is likely not exactly IBM's fault.
JMS Exceptions have always been very misleading, in my experience, for a particular reason. JMS is intentionally provider neutral. That means that all the Exceptions that are available are also provider neutral - which means that when MQ is being used with JMS, the development staff had to try their best to match up MQ Reason Codes with JMS Exceptions... and there's only a limited amount of correspondance possible.
Now, on the other hand, if you looked at CCSIDs because the MQ Reason Code lead you to look at that, or because there was an error in the MQ error log that lead you to that... then that is a different story.
But as mquseless said... you didn't give us enough information to know which of these two things you saw, and what lead you down the wrong path.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Dec 08, 2005 5:02 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Could you at least post the output of dspmqver along with the actual exception that you got? I'd be interested in seeing both. Also, since this is a client connection, I'd like to see your runmqsc output of your svrconn channel. |
|
| Back to top |
|
|
|
|
