| Author |
Message
|
| Blomman |
 Posted: Mon Feb 12, 2007 5:59 am Post subject: REASON:2150 |
 |
|
Master
Joined: 31 Oct 2006
Posts: 230
|
Hi all!
This is my scenario:
QM01(CCSID 819) -> BROKER(CCSID 1051) -> QM02(CCSID 819)
When the messages are going from broker to QM02 im getting this in log(se below).
I think the sender channel is doing an MQGET from tranmissionQ and it fails trying to convert the message?
And yes there is some kinda of conversion error here the message is in XML and includes "åäö". The message length is 92800.
Any ideas???
"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.
-------------------------------------------------------------------------------
02/12/07 11:47:52
AMQ9544: Messages not put to destination queue.
EXPLANATION:
During the processing of channel 'QMBRK01.QMPGD01' 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 '1511'.
" |
|
| Back to top |
|
 |
| exerk |
| Posted: Mon Feb 12, 2007 6:07 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Quote: |
| /var/mqm/exits//MQHRF2_r |
That's the obvious thing that catches my eye.
| Quote: |
| If the reason code occurs on the MQGET call, check that the data in the message is valid, and that the logic in the data-conversion exit is correct. |
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Blomman |
| Posted: Mon Feb 12, 2007 6:10 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
| exerk wrote: |
| Quote: |
| /var/mqm/exits//MQHRF2_r |
That's the obvious thing that cateches my eye.
| Quote: |
| If the reason code occurs on the MQGET call, check that the data in the message is valid, and that the logic in the data-conversion exit is correct. |
|
I dont have this exit...Never had!
And why is trying too "call" this exit???
I have other messages going through the broker, converting on channel "level"
and it works just fine and dont "call" som kind of exit that dosent exists..
/Micke |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Feb 12, 2007 6:18 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Go here:
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp
Search on:
MQRC_DBCS_ERROR
Then look in:
'API completion and reason codes'
For the 2150 code
Hope this helps guide you 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Feb 12, 2007 6:27 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
The error msg means that there has been some kind of conversion error.
When that happens, WMQ tries to find an exit to convert the data, and does not distinguish between internal and user-defined formats.
The title of the post says the reason is 2150 (MQRC_DBCS_ERROR). Where did that come from? The error msg does not have that reason code, and besides, 819 <-> 1051 cannot cause a DBCS error since they are both single-byte code pages.
Since the channel has been so obliging as to put the msgs to the local DLQ (on QM01), a browse of the DLQ (amqsbcg output) would provide useful information.
The most likely cause is either a badly formed msg, or there is no conversion table from 1208 to 819. The reason I say 1208 is that the name/value pairs in an RFH2 msg must be in code page 1208.
On HPUX the conversion table from 1208 -> 819 is /usr/lib/nls/iconv/tables/ucs2=iso81. The alias for the conversion must exist in /usr/lib/nls/iconv/config.iconv. If HPUX was recently upgraded on the machine the WQ aliases may have been lost; the solution is to run /opt/mqm/bin/reset_iconv_table.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| Blomman |
| Posted: Mon Feb 12, 2007 6:38 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
| Nigelg wrote: |
The title of the post says the reason is 2150 (MQRC_DBCS_ERROR). Where did that come from? |
Sorry this is the reasoncode from the message DLQ header on the broker.
/Micke |
|
| Back to top |
|
|
| Blomman |
| Posted: Mon Feb 12, 2007 6:42 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
Thx i have already been looking there...And it didnt really help me.
/Micke |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Feb 12, 2007 8:23 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Read a little farther into my post...
| Quote: |
Since the channel has been so obliging as to put the msgs to the local DLQ (on QM01), a browse of the DLQ (amqsbcg output) would provide useful information.
|
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| Blomman |
| Posted: Mon Feb 12, 2007 12:45 pm Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
| Nigelg wrote: |
Read a little farther into my post...
| Quote: |
Since the channel has been so obliging as to put the msgs to the local DLQ (on QM01), a browse of the DLQ (amqsbcg output) would provide useful information.
|
|
Nix it is obliging to put and are putting on DLQ on broker...
And why use amqsbcg? I browse the message using RFHUtil.
/Micke |
|
| Back to top |
|
|
| Nigelg |
| Posted: Tue Feb 13, 2007 1:32 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
The idea of using amqsbcg was that you could browse the msg and post it here, so we could check it.
However, I am not going to beg you to allow me to help you. I wish you every success in solving your problem without my help.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| Blomman |
| Posted: Tue Feb 13, 2007 2:44 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
| Nigelg wrote: |
The idea of using amqsbcg was that you could browse the msg and post it here, so we could check it.
However, I am not going to beg you to allow me to help you. I wish you every success in solving your problem without my help. |
Hi im very gratful that u help me on this one..
I tryed to use amqsbcg, but some kind of error occured i think the message is to big.
Can i post the message here, browsing it from RFHUtil? Would that help?
/Micke |
|
| Back to top |
|
|
| Blomman |
| Posted: Tue Feb 13, 2007 7:37 am Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
Found the problem...
MQMD = 819
RFH = 1280
/Micke |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Feb 13, 2007 3:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Blomman wrote: |
Found the problem...
MQMD = 819
RFH = 1280
/Micke |
Looks like the good old typo devil is laughing again 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Blomman |
| Posted: Tue Feb 13, 2007 11:57 pm Post subject: |
|
|
Master
Joined: 31 Oct 2006
Posts: 230
|
| fjb_saper wrote: |
| Blomman wrote: |
Found the problem...
MQMD = 819
RFH = 1280
/Micke |
Looks like the good old typo devil is laughing again |
Programmers...Programmers...When are they going to do things right.. |
|
| Back to top |
|
|
| Julia |
| Posted: Mon Feb 19, 2007 8:37 am Post subject: MQRC_DBCS_ERROR on double byte character 1208 --> 819 |
|
|
Newbie
Joined: 15 Feb 2007
Posts: 3
Location: France
|
Hi,
I am working on a similar problem, a 2150, since last week and I thought maybe you could help. My problem seems to correspond to the case described by Nigelg, since it happens on a conversion between 1208 and 819:
| Nigelg wrote: |
...
The most likely cause is either a badly formed msg, or there is no conversion table from 1208 to 819. The reason I say 1208 is that the name/value pairs in an RFH2 msg must be in code page 1208.
...
|
After a lot of analyzes I see that the problem occurs on the UTF-8 double byte character U+00B0 or "c2 b0", i.e. the degree sign. On other double byte characters like é (U+00E9 or "c3 a9") I do not get a 2150, but the conversion is not done properly. There are characters missing in the end.
I have MQ version 5.3 CSD 4 on Solaris 8. I do not have any conversion table between 1208 and 819 and I cannot find any either. Do you know if it exists? In my file with default conversions I see that CCSID 1208 is based on CCSID 13488, but then I have nothing in the column DBCS. I guess this is the problem... Could someone please give me a hint what to do in order to make the conversion 1208 --> 819 work even with double byte characters? Thank you!
# CCSID Base CodePage CodePage Type Enc ACRI Codeset
# CCSID DBCS SBCS name
# ----- ----- -------- -------- ---- ---- ----- -------
1208 13488 0 13488 3 5 0 UTF-8 |
|
| Back to top |
|
|
|
|
