| Author |
Message
|
| Lisa |
 Posted: Wed Jul 31, 2002 5:11 am Post subject: Conversion Not Supported |
 |
|
Master
Joined: 07 Jun 2002
Posts: 287
Location: NJ
|
All,
I'm running my message flows on HP-UX 11.
The message flows do not contain hard coded CCSID statements, I use the MQMD.CCSID in my CAST statements.
Here are the errors that occur in the MQSeries error log file:
Can someone explain why these error messages appear in the error log?
Thanks, Lisa
07/30/02 16:52:23
AMQ6047: Conversion not supported.
EXPLANATION:
MQSeries is unable to convert string data tagged in CCSID 1208 to data in CCSID
437.
ACTION:
Check the appropriate National Language Support publications to see if the
CCSIDs are supported by your system.
07/30/02 16:52:23
AMQ6174: The library /var/mqm/exits//MQHRF2_r was not found. The queue manager
will continue without this module.
EXPLANATION:
The dynamically loadable file /var/mqm/exits//MQHRF2_r was not found.
ACTION:
Check that the file exists and is either fully qualified or is in the
appropriate directory.
07/30/02 16:52:23
AMQ9544: Messages not put to destination queue.
EXPLANATION:
During the processing of channel 'PIIHPP02.TO.PIINTP01' one or more messages
could not be put to the destination queue and attempts were made to put them to
a dead-letter queue. The location of the queue is 1, where 1 is the local
dead-letter queue and 2 is the remote dead-letter queue.
ACTION:
Examine the contents of the dead-letter queue. Each message is contained in a
structure that describes why the message was put to the queue, and to where it
was originally addressed. Also look at previous error messages to see if the
attempt to put messages to a dead-letter queue failed. The program identifier
(PID) of the processing program was '15239'. |
|
| Back to top |
|
 |
| JLRowe |
| Posted: Wed Jul 31, 2002 5:39 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
conversion not supported:
You have characters in unicode (1208) that are not present in codepage 437, therefore WMQI cannot do the conversion. (I think) character tables are in the MQSeries documentation somewhere. |
|
| Back to top |
|
|
| Lisa |
| Posted: Wed Jul 31, 2002 5:48 am Post subject: Conversion |
|
|
Master
Joined: 07 Jun 2002
Posts: 287
Location: NJ
|
The errors appear whenever I delpoy message flows from our NT workstation to HP.
For example, I just deployed one message flow and the following information appeared in our error log:
Thanks, Lisa
...skipping forward
07/31/02 09:58:55
AMQ9002: Channel program started.
EXPLANATION:
Channel program 'PIINTD01.TO.PIIHPD01' started.
ACTION:
None.
-------------------------------------------------------------------------------
07/31/02 09:59:07
AMQ9002: Channel program started.
EXPLANATION:
Channel program 'PIIHPD01.TO.PIINTD01' started.
ACTION:
None.
-------------------------------------------------------------------------------
07/31/02 09:59:08
AMQ6047: Conversion not supported.
EXPLANATION:
MQSeries is unable to convert string data tagged in CCSID 1208 to data in CCSID
437.
ACTION:
Check the appropriate National Language Support publications to see if the
CCSIDs are supported by your system.
-------------------------------------------------------------------------------
07/31/02 09:59:08
AMQ6174: The library /var/mqm/exits//MQHRF2_r was not found. The queue manager
will continue without this module.
EXPLANATION:
The dynamically loadable file /var/mqm/exits//MQHRF2_r was not found.
ACTION:
Check that the file exists and is either fully qualified or is in the
appropriate directory.
-------------------------------------------------------------------------------
07/31/02 09:59:08
AMQ6047: Conversion not supported.
EXPLANATION:
MQSeries is unable to convert string data tagged in CCSID 1208 to data in CCSID
437.
ACTION:
Check the appropriate National Language Support publications to see if the
CCSIDs are supported by your system. |
|
| Back to top |
|
|
| Lisa |
| Posted: Wed Jul 31, 2002 6:17 am Post subject: Conversion |
|
|
Master
Joined: 07 Jun 2002
Posts: 287
Location: NJ
|
All,
Here a message from our SYSTEM.DEAD.LETTER.QUEUE.
MQGET of message number 177
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 1051
Format : 'MQDEAD '
Priority : 0 Persistence : 0
MsgId : X'414D51205049494850443031202020203D3F1053000B3262'
CorrelId : X'4366674D6772537562330000000000000000000000000000'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'PIIHPD01 '
** Identity Context
UserIdentifier : 'mqsiuid '
AccountingToken :
X'0000000000000000000000000000000000000000000000000000000000000000'
ApplIdentityData : ' '
** Origin Context
PutApplType : '26'
PutApplName : 'PIIHPD01_BKR '
PutDate : '20020731' PutTime : '14051723'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 639 bytes
00000000: 444C 4820 0000 0001 0000 0847 5359 5354 'DLH .......GSYST'
00000010: 454D 2E42 524F 4B45 522E 4144 4D49 4E2E 'EM.BROKER.ADMIN.'
00000020: 5245 504C 5920 2020 2020 2020 2020 2020 'REPLY '
00000030: 2020 2020 2020 2020 2020 2020 5049 494E ' PIIN'
00000040: 5444 3031 2020 2020 2020 2020 2020 2020 'TD01 '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 0000 0111 ' ....'
00000070: 0000 04B8 4D51 4852 4632 2020 0000 0006 '....MQHRF2 ....'
00000080: 7275 6E6D 7163 686C 5F6E 6420 2020 2020 'runmqchl_nd '
00000090: 2020 2020 2020 2020 2020 2020 3230 3032 ' 2002'
000000A0: 3037 3331 3134 3035 3137 3330 5246 4820 '073114051730RFH '
000000B0: 0000 0002 0000 0100 0000 0111 0000 04B8 '................'
000000C0: 2020 2020 2020 2020 0000 0000 0000 04B8 ' ........'
000000D0: 0000 00B8 3C70 7363 3E3C 436F 6D6D 616E '....<psc><Comman'
000000E0: 643E 5075 626C 6973 683C 2F43 6F6D 6D61 'd>Publish</Comma'
000000F0: 6E64 3E3C 514D 6772 4E61 6D65 3E50 4949 'nd><QMgrName>PII'
00000100: 4850 4430 315F 424B 523C 2F51 4D67 724E 'HPD01_BKR</QMgrN'
00000110: 616D 653E 3C51 4E61 6D65 3E53 5953 5445 'ame><QName>SYSTE'
00000120: 4D2E 4252 4F4B 4552 2E43 4F4E 5452 4F4C 'M.BROKER.CONTROL'
00000130: 2E51 5545 5545 3C2F 514E 616D 653E 3C54 '.QUEUE</QName><T'
00000140: 6F70 6963 3E24 5359 532F 4272 6F6B 6572 'opic>$SYS/Broker'
00000150: 2F50 4949 4850 4430 315F 424B 522F 5374 '/PIIHPD01_BKR/St'
00000160: 6174 7573 2F45 7865 6375 7469 6F6E 4772 'atus/ExecutionGr'
00000170: 6F75 702F 6465 6661 756C 743C 2F54 6F70 'oup/default</Top'
00000180: 6963 3E3C 2F70 7363 3E20 2020 0000 001C 'ic></psc> ....'
00000190: 3C6D 6364 3E3C 4D73 643E 786D 6C3C 2F4D '<mcd><Msd>xml</M'
000001A0: 7364 3E3C 2F6D 6364 3E20 2020 3C42 726F 'sd></mcd> <Bro'
000001B0: 6B65 7220 7575 6964 3D22 6364 3366 3961 'ker uuid="cd3f9a'
000001C0: 6366 2D65 6430 302D 3030 3030 2D30 3038 'cf-ed00-0000-008'
000001D0: 302D 6566 3836 6263 6237 6432 6331 223E '0-ef86bcb7d2c1">'
000001E0: 3C45 7865 6375 7469 6F6E 4772 6F75 7020 '<ExecutionGroup '
000001F0: 7575 6964 3D22 3738 6265 3961 6366 2D65 'uuid="78be9acf-e'
00000200: 6430 302D 3030 3030 2D30 3038 302D 6566 'd00-0000-0080-ef'
00000210: 3836 6263 6237 6432 6331 223E 3C53 7461 '86bcb7d2c1"><Sta'
00000220: 7274 3E3C 4D65 7373 6167 6546 6C6F 7720 'rt><MessageFlow '
00000230: 7575 6964 3D22 3437 3336 6261 3134 2D65 'uuid="4736ba14-e'
00000240: 6630 302D 3030 3030 2D30 3038 302D 6566 'f00-0000-0080-ef'
00000250: 3836 6263 6237 6432 6331 222F 3E3C 2F53 '86bcb7d2c1"/></S'
00000260: 7461 7274 3E3C 2F45 7865 6375 7469 6F6E 'tart></Execution'
00000270: 4772 6F75 703E 3C2F 4272 6F6B 6572 3E 'Group></Broker> '
|
|
| Back to top |
|
|
| JLRowe |
| Posted: Wed Jul 31, 2002 9:00 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
The errors occur during the deploy?? Thats weird, you must have set up MQSeries in a strange way.
Did you specify CONVERT(YES) on the sender channels by any chance? |
|
| Back to top |
|
|
| Lisa |
| Posted: Wed Jul 31, 2002 9:15 am Post subject: Conversion |
|
|
Master
Joined: 07 Jun 2002
Posts: 287
Location: NJ
|
Yes!
CONVERT is equal to YES. |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Jul 31, 2002 9:22 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
I don't think you need to set CONVERT option for the channels defined between Configuration Manager's and Brokers's queue managers. Try setting CONVERT option to NO and see if the problem gets solved after this.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| JLRowe |
| Posted: Wed Jul 31, 2002 11:39 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
| Yes, it looks like CONVERT(YES) is the culprit. The broker and the configuration manager are responsible for data conversion, setting CONVERT(YES) is forcing MQSeries to call a non-existent data conversion exit and causing all the errors. |
|
| Back to top |
|
|
| Lisa |
| Posted: Wed Jul 31, 2002 12:22 pm Post subject: Conversion |
|
|
Master
Joined: 07 Jun 2002
Posts: 287
Location: NJ
|
I'll make the change and post the results.
Thanks for your help.
Lisa |
|
| Back to top |
|
|
| sgopal |
| Posted: Wed Jul 31, 2002 1:47 pm Post subject: |
|
|
Acolyte
Joined: 30 Jul 2002
Posts: 63
|
| Data Conversion is usually done by the target application. Try coding the convert explicitly on the MQGET call instead of the channel convert parameter. That way you can prevent messages from ending up on the system dead letter queue. Channel CONVERT is generaly used when the environment on which the Remote Queue Manager resides does not support data conversion. |
|
| Back to top |
|
|
|
|
