Author |
Message
|
hdjur |
Posted: Wed Jun 14, 2006 5:07 am Post subject: conversion not supported while starting sender channels |
|
|
Centurion
Joined: 16 Sep 2004 Posts: 116 Location: Zagreb
|
Hello!
I am reading ccsid.table documentation over and over again, and I still need help. I have qmgr on Windows ccsid 437, and qmgr on AIX ccsid 912, both mqver are 5.3. Do I have to have 01B50390.tbl and 039001B5.tbl in folder C:\Program Files\IBM\WebSphere MQ\conv\table (because I don't have it), in order to be able to start channels in both directions? Which files am I probably missing on AIX (in which folder?)?
Can I solve the problem by simply editing C:\Program Files\IBM\WebSphere MQ\conv\table\ccsid.tbl on Windows machine? Do I have to edit /var/mqm/conv/table/ccsid.tbl on AIX machine? Shall I modify part of ccsid.tbl files regarding default conversion or something else? I have solved the problem temporary by altering qmgr on AIX setting ccsid to 437, starting channels in both directions, and then altering it back to 912. Whenever channels stop, connection can't be reestablished. I have to fix the problem permanently. Thanks in advance for any suggestion. |
|
Back to top |
|
 |
Nigelg |
Posted: Wed Jun 14, 2006 5:54 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
912 is ISO8859-2, Latin 2, Eastern European.
The Windows equivalent is not 437, but 1250/5346 (with/without Euro).
You should change the CCSID of the Windows qmgr to 1250 (0x4E2) or 5346 (0x14E2) and then the conversion will be possible.
The files 04E20390.tbl, 039004E2.tbl, 14E20390.tbl, 039014E2.tbl are issued as part of the WMQ AIX installation, so the conversions 912<-> 1250 and 912<->5346 are supported. _________________ MQSeries.net helps those who help themselves.. |
|
Back to top |
|
 |
tleichen |
Posted: Wed Jun 14, 2006 5:57 am Post subject: Re: conversion not supported while starting sender channels |
|
|
Yatiri
Joined: 11 Apr 2005 Posts: 663 Location: Center of the USA
|
hdjur wrote: |
I am reading ccsid.table documentation over and over again, and I still need help. I have qmgr on Windows ccsid 437, and qmgr on AIX ccsid 912, both mqver are 5.3. Do I have to have 01B50390.tbl and 039001B5.tbl in folder C:\Program Files\IBM\WebSphere MQ\conv\table (because I don't have it), in order to be able to start channels in both directions? |
Why would you be missing codeset conversion files?  _________________ IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
Back to top |
|
 |
hdjur |
Posted: Wed Jun 14, 2006 7:33 am Post subject: |
|
|
Centurion
Joined: 16 Sep 2004 Posts: 116 Location: Zagreb
|
Nigel, is there any way to keep ccsid 437 on Windows machine, and to be able to start channels to and from AIX qmgr with ccsid 912? |
|
Back to top |
|
 |
hdjur |
Posted: Wed Jun 14, 2006 7:52 am Post subject: |
|
|
Centurion
Joined: 16 Sep 2004 Posts: 116 Location: Zagreb
|
Tleichen, I don't know, that's why I'm asking. You suggest that these files are not needed during channel's start? |
|
Back to top |
|
 |
mqmaniac |
Posted: Fri Jun 16, 2006 7:51 am Post subject: |
|
|
 Master
Joined: 27 Dec 2005 Posts: 201
|
Hdjur,
Pls Mention What are you trying to do and what is the Issue you have..
You just mentioned Issue when you are trying to do "something" which is not mentioned in your post!
Pls Elaborate!! |
|
Back to top |
|
 |
hdjur |
Posted: Sun Jun 18, 2006 1:58 pm Post subject: |
|
|
Centurion
Joined: 16 Sep 2004 Posts: 116 Location: Zagreb
|
Hi mqmaniac!
I'm trying to start sender channel from a qmgr with ccsid=912 to a qmgr with ccsid=437 (and in opposite direction too). It will not start, it goes to a retrying mode. If I ping channel, it reports "conversion not supported". The issue is that I would like to keep ccsid of qmgrs as they are now, and to be able to start channels between them. Is it possible, if yes, what do I have to do? Thank you. |
|
Back to top |
|
 |
hdjur |
Posted: Sun Jun 18, 2006 2:15 pm Post subject: |
|
|
Centurion
Joined: 16 Sep 2004 Posts: 116 Location: Zagreb
|
Qmgr logs when I try to ping channel:
19.06.2006 00:01:27
AMQ6047: Conversion not supported.
EXPLANATION:
WebSphere MQ is unable to convert string data tagged in CCSID 912 to data in
CCSID 437.
ACTION:
Check the WebSphere MQ Application Programming Reference Appendix and the
appropriate National Language Support publications to see if the CCSIDs are
supported by your system.
----- amquopra.c : 3906 -------------------------------------------------------
I believe 437 is not supported - how can I check it, and do I have to contact my OS administrator to install support, or can I do something by administrating ccsid.tbl? |
|
Back to top |
|
 |
fjb_saper |
Posted: Sun Jun 18, 2006 3:21 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Have you checked whether you have the channel conversion attribute set ?
 _________________ MQ & Broker admin |
|
Back to top |
|
 |
hdjur |
Posted: Mon Jun 19, 2006 12:03 am Post subject: |
|
|
Centurion
Joined: 16 Sep 2004 Posts: 116 Location: Zagreb
|
I have CONVERT(NO) attribute set. |
|
Back to top |
|
 |
Nigelg |
Posted: Mon Jun 19, 2006 12:40 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004 Posts: 1046
|
I have already answered this, the 437 <-> 912 conversion.
Also, the conversion here is at channel startup, not when passing msgs. _________________ MQSeries.net helps those who help themselves.. |
|
Back to top |
|
 |
hdjur |
Posted: Fri Jul 28, 2006 8:54 am Post subject: |
|
|
Centurion
Joined: 16 Sep 2004 Posts: 116 Location: Zagreb
|
Hello everyone!
Although I have received an authoritative answer by Nigelg:
Quote: |
You should change the CCSID of the Windows qmgr to 1250 (0x4E2) or 5346 (0x14E2) and then the conversion will be possible.
|
and
Quote: |
I have already answered this, the 437 <-> 912 conversion.
|
I must admit that I succeeded to make conversion possible in cooperation with our OS administrator without altering CCSID on a qmgr. If there are such conditions on the host:
$ uname
AIX
$ iconv -l|grep 437
$
. . . I can't start channel to a desired Windows qmgr, without altering qmgr's CCSID to 437 on AIX side. But if there is:
$ uname
AIX
$ iconv -l|grep 437
$ IBM-437
$
. . . channel starts without problem with CCSID set to 912.
Since our OS admin is an authoritative person too, I didn't get full explanation about the magic behind this behaviour, ie how exactly did he install this character support, but, little by little, I gather information about things I'm interested in. By the way, I knew this (at least I supposed so):
Quote: |
Also, the conversion here is at channel startup, not when passing msgs.
|
I was just answering to fjb_saper's question.
Still, when I use Paul Clarke's mo71 support pack, on the same PC I'm able to perform remote administration of qmgr on some Solaris machine with CCSID set to 819 without any problem, and for some other qmgr on AIX I receive this:
CCSID error. CCSID = 819.
I don't know how to avoid a problem with conversion on svrconn channel (I'm using client configured connection). I get this info when I look at that moment at channel status:
dis chs(SYSTEM.DEF.SVRCONN)
AMQ8417: Display Channel Status details.
CHANNEL(SYSTEM.DEF.SVRCONN) CHLTYPE(SVRCONN)
CONNAME(10.x.x.x) CURRENT
RQMNAME( ) STATUS(RUNNING)
SUBSTATE(RECEIVE) XMITQ( )
AMQ8417: Display Channel Status details.
CHANNEL(SYSTEM.DEF.SVRCONN) CHLTYPE(SVRCONN)
CONNAME(10.x.x.x) CURRENT
RQMNAME( ) STATUS(RUNNING)
SUBSTATE(MQGET) XMITQ( )
What would be normal way to handle this issue? Altering CCSID on a targeted qmgr, editing ccsid.tbl on my PC (what to change?), installing another missing character support on a targeted AIX? Thanks in advance. |
|
Back to top |
|
 |
hdjur |
Posted: Tue Aug 01, 2006 1:08 am Post subject: |
|
|
Centurion
Joined: 16 Sep 2004 Posts: 116 Location: Zagreb
|
Hello!
Quote: |
The files 04E20390.tbl, 039004E2.tbl, 14E20390.tbl, 039014E2.tbl are issued as part of the WMQ AIX installation |
Where are these files kept? On windows machine I located them in this folder: C:\Program Files\IBM\WebSphere MQ\conv\table
On AIX it should be in: /var/mqm/conv/table
But there I have only this file: ccsid.tbl
Despite of that, conversions are supported. What are these files needed for? Are they located somewhere else? I couldn't find them anywhere.
Could someone please tell url of the document (somewhere near http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp ) which describes precisly the purpose of all files which are part of the WMQ AIX installation, and description of all processes which are part of WMQ server instance, and processes that implement other functions related to MQ?
Thanks. |
|
Back to top |
|
 |
hdjur |
Posted: Fri Sep 01, 2006 9:14 am Post subject: |
|
|
Centurion
Joined: 16 Sep 2004 Posts: 116 Location: Zagreb
|
Here I go again with conversion not supported problems.
First, let me say that I solved the problem with mo71 by performing endmqcsv and strmqcsv on a server host.
I have ccsid set to 819 on nearly half of our qmgrs and 912 on the other nearly half. The only qmgrs who have setting 437 are those, which I am forced to keep that way. I have default conversion on my PC defined as: 852 xxx. If I make equal xxx and ccsid on a remote qmgr, I'm able to connect and perform remote administration. Sometimes, this is not neccessary. I make it equal by editing ccsid.tbl on my PC and restarting mo71, or by altering qmgr and restarting command server. The obvious solution to this problem is to have all qmgrs with the same setting.
Another problem regarding conversion not supported.
I was reported about MQRC_CLUSTER_RESOLUTION_ERROR, on one Linux server. I have noticed FDC files with this:
Probe Id :- XC076001
Major Errorcode :- xecF_E_UNEXPECTED_RC
Minor Errorcode :- xecX_E_CONV_NOT_SUP
I have set (according to some advices found on the internet by our sysadmin):
export LC_ALL="C"
export LANG="C"
instead of previous :
export LC_ALL="hr_HR"
export LANG="hr_HR"
and restarted qmgr with proper environment, xinetd too (with kill -1).
At first it solved the problem after cluster refresh. But, since FDC files were still produced, I have deleted qmgr (I forgot to suspend it), recreated it with proper environment, started it, and refreshed the cluster.
And then real problems started. I can't connect it to a cluster. Full repository qmgr is listed on this qmgr with:
CLUSQMGR(SYSTEM.TEMPQMGR...)
CLUSRCVR and CLUSSDR are running, but obviously qmgr receives no data from full repository. Now I have MQRC_UNKNOWN_OBJECT_NAME when trying to put to a clustered queue not hosted by this qmgr, instead of previous MQRC_CLUSTER_RESOLUTION_ERROR.
And FDC files are still produced, with this Probe Id. Any suggestions? Like higer CMVC level?
$ dspmqver
Name: WebSphere MQ
Version: 6.0.0.0
CMVC level: p000-L050519
BuildType: IKAP - (Production)
$ uname -a
Linux xxx 2.6.5-7.97-smp #1 SMP Fri Jul 2 14:21:59 UTC 2004 i686 i686 i386 GNU/Linux
Still I wonder, why is MCP (message channel protocol) designed that way, to be sensitive about conversion support? |
|
Back to top |
|
 |
|