| Author |
Message
|
| tkaravind |
 Posted: Mon May 24, 2004 5:39 am Post subject: CCSID errors in Client-Server connection... |
 |
|
Acolyte
Joined: 24 Jul 2001
Posts: 60
|
Dear All,
We have a client -server MQSeries environment in Windows 2K where the client machines suddenly started throwing a 2059.
The message in the log shows this :
"The program ended because either the Source ccsid 437 or TARGET CCSID 1381 is not valid OR NOT CURRENTLY SUPPORTED...CORRECT THIS"
What does this mean and how can it be corrected ?
The operators told me there was absoultely no change done on the settings but somehow this error came all of a sudden !!!
Your help is highly appreciated.
Thanks,
Aravind |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon May 24, 2004 6:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That's likely an application error message.
Reason Code 2059 is Queue Manager Not Available.
Likely, the client channel is failing for some reason or another - and the application is written to claim that this is because of a conversion issue - which is likely not the real issue.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| vijiraghav |
| Posted: Tue May 25, 2004 8:44 pm Post subject: CCSID errors in Client-Server connection... |
|
|
Novice
Joined: 11 Nov 2003
Posts: 18
|
Hi
You may please try setting the SYSTEM environmental variable MQCCSID on Windows client pc as 1381.
set MQCCSID=1381
Vijiraghav |
|
| Back to top |
|
|
| shogan2003 |
| Posted: Wed May 26, 2004 4:08 am Post subject: |
|
|
Centurion
Joined: 03 Jul 2003
Posts: 133
Location: London
|
Have you tried running a trace on the client machine ?
Steps
------
1. strmqtrc.exe
2. Run client app
3. endmqtrc
4. Find latest copies of *.TRC on client platform
_________________
MQSI2 certified specialist
MQSeries certified specialist |
|
| Back to top |
|
|
| tkaravind |
| Posted: Thu May 27, 2004 10:08 pm Post subject: |
|
|
Acolyte
Joined: 24 Jul 2001
Posts: 60
|
Dear All,
Thanks for your help. The problem got fixed when we changed the
Local settings to "English (US)" on the client machine. (It was originally set to Chinese)
I think without this the MQSeries client was unable to interpret the Channel Tab file (which I saw had some Chinese characters !!!) and hence could not locate the queue manager.
Were you aware of this !!!
Regards,
Aravind |
|
| Back to top |
|
|
| EddieA |
| Posted: Fri May 28, 2004 8:51 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Not sure if that really was your problem.
| Quote: |
| Channel Tab file (which I saw had some Chinese characters !!!) |
That table is a binary file, and so can contain ANY hex value. These may look like Chinese characters, but they aren't. Also, MQ doesn't support names in anything other than A-Z, 1-9, and a couple of special characters.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| leongor |
| Posted: Sun May 30, 2004 7:43 am Post subject: |
|
|
Master
Joined: 13 May 2002
Posts: 264
Location: Israel
|
| Quote: |
The program ended because either the Source ccsid 437 or TARGET CCSID 1381 is not valid OR NOT CURRENTLY SUPPORTED...CORRECT THIS
|
It describes the situation as it is : you cannot convert chinese to english.
In this case you should use unicode (1208) or set default data conversion in ccsid.tbl to multilingual (850):
default 0 850 1 2 0
_________________
Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
| Back to top |
|
|
|
|
