| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Code page issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| kirank |
 Posted: Tue Aug 17, 2010 11:00 am Post subject: Code page issue |
 |
|
Centurion
Joined: 10 Oct 2002
Posts: 136
Location: California
|
Hi,
I have an interface where we get XML message from a .Net application. The application is setting the MQ Header CCSID to 1208 and sending the message. The message is transformed by Broker which is on AIX. After Transforming when Broker tries to write the message to target MQ queue which is on HP-UX server, It gets an error unconvertable character. I am including partial trace for the flow below
2010-08-09 14:20:28.255142 5912 UserTrace BIP2537I: Node 'EMM_SOSUBMIT_BAPI_SALESORDER.Compute': Executing statement ''RETURN TRUE;'' at ('.EMM_SOSUBMIT_BAPI_SALESORDER_Compute.main', '259.3').
2010-08-09 14:20:28.255244 5912 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'EMM_SOSUBMIT_BAPI_SALESORDER.Compute'.
2010-08-09 14:20:28.255956 5912 UserTrace BIP2231E: Error detected whilst processing a message in node 'EMM_SOSUBMIT_BAPI_SALESORDER.DestinationQueues'.
The message broker detected an error whilst processing a message in node 'EMM_SOSUBMIT_BAPI_SALESORDER.DestinationQueues'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2010-08-09 14:20:28.255964 5912 ParserException BIP5010E: XML Writing Errors have occurred.
Errors have occurred during writing of XML.
Review further error messages for an indication to the cause of the errors.
2010-08-09 14:20:28.255976 5912 RecoverableException BIP2136E: Source character ''2026'' in field ''004e00530031003a007300610070005f007a006f0072006400650072005f007400650078007
4002000730069007a0065003d002200310022003e003c004e00530034003a0073006100700
05f007a006f0072006400650072005f007400650078007400200078006d006c006e0073003a
004e00530034003d00220068007400740070003a002f002f007700770077002e0069006200
6d002e0063006f006d002f007700650062007300700068006500720065002f00630072006f0
07300730077006f0072006c00640073002f0032003000300032002f0042004f005300630068
0065006d0061002f007300610070005f007a006f0072006400650072005f0074006500780074
0022003e003c004e00530034003a0054004500580054005f00490044003e005a0043004f004
e003c002f004e00530034003a0054004500580054005f00490044003e003c004e0053003400
3a004c0041004e00470055003e0045003c002f004e00530034003a004c0041004e004700550
03e003c004e00530034003a0054004500580054005f004c0049004e0045003e004a0020006f
006e00200038002f0035002f003200300031003000200033003a00310034003a0033003500
20006e00200038002f0035002f003200300031003000200039003a00330034003a00310033
00200041004d003a002000430020006f006e00200033002f00330031002f00320030003100
3000200031003a00300031003a0032003700200050004d003a00200053006f20262026002e
006900730020003f007c002d007c003c002f004e00530034003a0054004500580054005f004c
0049004e0045003e003c002f004e00530034003a007300610070005f007a006f00720064006
50072005f0074006500780074003e003c002f004e00530031003a007300610070005f007a00
6f0072006400650072005f0074006500780074003e003c002f004e00530031003a007300610
070005f007a0062006100700069005f00730064005f006300720065006100740065005f0077
007200610070003e'' cannot be converted from unicode to codepage '819'.
The source character is an invalid code point within the given codepage.
Correct the application or message flow that generated the message to ensure that all data within the message can be represented in the target codepage.
2010-08-09 14:20:28.257354 5912 Error BIP2232E: Error detected whilst handling a previous error in node 'EMM_SOSUBMIT_BAPI_SALESORDER.SAP.ERROR'.
The message broker has detected an error in node 'EMM_SOSUBMIT_BAPI_SALESORDER.SAP.ERROR' whilst handling a previous error.
See the following messages for details of the exception list associated with the original error. Thereafter messages will be associated with the new error.
2010-08-09 14:20:28.257366 5912 RecoverableException BIP2230E: Error detected whilst processing a message in node 'EMM_SOSUBMIT_BAPI_SALESORDER.DestinationQueues'.
The message broker detected an error whilst processing a message in node 'EMM_SOSUBMIT_BAPI_SALESORDER.DestinationQueues'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2010-08-09 14:20:28.257372 5912 ParserException BIP5010E: XML Writing Errors have occurred.
Errors have occurred during writing of XML.
Review further error messages for an indication to the cause of the errors.
2010-08-09 14:20:28.257384 5912 RecoverableException BIP2136E: Source character ''2026'' in field ''004e00530031003a007300610070005f007a006f0072006400650072005f0074006500780074
002000730069007a0065003d002200310022003e003c004e00530034003a007300610070005f
007a006f0072006400650072005f007400650078007400200078006d006c006e0073003a004e0
0530034003d00220068007400740070003a002f002f007700770077002e00690062006d002e00
63006f006d002f007700650062007300700068006500720065002f00630072006f007300730077
006f0072006c00640073002f0032003000300032002f0042004f0053006300680065006d006100
2f007300610070005f007a006f0072006400650072005f00740065007800740022003e003c004e
00530034003a0054004500580054005f00490044003e005a0043004f004e003c002f004e00530
034003a0054004500580054005f00490044003e003c004e00530034003a004c0041004e00470
055003e0045003c002f004e00530034003a004c0041004e00470055003e003c004e005300340
03a0054004500580054005f004c0049004e0045003e004a0020006f006e00200038002f003500
2f003200300031003000200033003a00310034003a003300350020006e00200038002f003500
2f003200300031003000200039003a00330034003a0031003300200041004d003a0020004300
20006f006e00200033002f00330031002f003200300031003000200031003a00300031003a00
32003700200050004d003a00200053006f20262026002e006900730020003f007c002d007c003c
002f004e00530034003a0054004500580054005f004c0049004e0045003e003c002f004e005300
34003a007300610070005f007a006f0072006400650072005f0074006500780074003e003c002f
004e00530031003a007300610070005f007a006f0072006400650072005f0074006500780074
003e003c002f004e00530031003a007300610070005f007a0062006100700069005f007300640
05f006300720065006100740065005f0077007200610070003e'' cannot be converted from unicode to codepage ''819''.
The source character is an invalid code point within the given codepage.
Correct the application or message flow that generated the message to ensure that all data within the message can be represented in the target codepage.
2010-08-09 14:20:28.257652 5912 UserTrace BIP2231E: Error detected whilst processing a message in node 'EMM_SOSUBMIT_BAPI_SALESORDER.LOCAL.SOSUBMIT_EMM'.
The message broker detected an error whilst processing a message in node 'EMM_SOSUBMIT_BAPI_SALESORDER.LOCAL.SOSUBMIT_EMM'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2010-08-09 14:20:28.257660 5912 RecoverableException BIP2230E: Error detected whilst processing a message in node 'EMM_SOSUBMIT_BAPI_SALESORDER.SAP.ERROR'.
The message broker detected an error whilst processing a message in node 'EMM_SOSUBMIT_BAPI_SALESORDER.SAP.ERROR'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2010-08-09 14:20:28.257668 5912 ParserException BIP5010E: XML Writing Errors have occurred.
Errors have occurred during writing of XML.
Review further error messages for an indication to the cause of the errors.
2010-08-09 14:20:28.257678 5912 RecoverableException BIP2136E: Source character ''2026'' in field ''004e00530031003a007300610070005f007a006f0072006400650072005f00740065007800740020
00730069007a0065003d002200310022003e003c004e00530034003a007300610070005f007a006f0
072006400650072005f007400650078007400200078006d006c006e0073003a004e00530034003d0
0220068007400740070003a002f002f007700770077002e00690062006d002e0063006f006d002f
007700650062007300700068006500720065002f00630072006f007300730077006f0072006c0064
0073002f0032003000300032002f0042004f0053006300680065006d0061002f007300610070005f
007a006f0072006400650072005f00740065007800740022003e003c004e00530034003a0054004
500580054005f00490044003e005a0043004f004e003c002f004e00530034003a005400450058005
4005f00490044003e003c004e00530034003a004c0041004e00470055003e0045003c002f004e0053
0034003a004c0041004e00470055003e003c004e00530034003a0054004500580054005f004c00490
04e0045003e004a0020006f006e00200038002f0035002f003200300031003000200033003a003100
34003a003300350020006e00200038002f0035002f003200300031003000200039003a0033003400
3a0031003300200041004d003a002000430020006f006e00200033002f00330031002f0032003000
31003000200031003a00300031003a0032003700200050004d003a00200053006f20262026002e
006900730020003f007c002d007c003c002f004e00530034003a0054004500580054005f004c004900
4e0045003e003c002f004e00530034003a007300610070005f007a006f0072006400650072005f007
4006500780074003e003c002f004e00530031003a007300610070005f007a006f0072006400650072
005f0074006500780074003e003c002f004e00530031003a007300610070005f007a006200610070
0069005f00730064005f006300720065006100740065005f0077007200610070003e'' cannot be converted from unicode to codepage '819'.
The source character is an invalid code point within the given codepage.
Correct the application or message flow that generated the message to ensure that all data within the message can be represented in the target codepage.
2010-08-09 14:20:28.257880 5912 UserTrace BIP4201I: Message propagated to out terminal from node 'EMM_SOSUBMIT_BAPI_SALESORDER.EAI_ERROR_FLOW.ResetContentDescriptor'.
A reset content descriptor node has received a message and is propagating it to any nodes connected to its out terminal.
No user action required.
I have copied the MQ headers from Input to output so the output has ccsid as 1208.
The error occurs when writing the message to target queue. The question is
1. Why is it trying to convert to code page 819?
2. Is there any way to force 1208 instead of 819?
Regards
Kiran |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Tue Aug 17, 2010 12:01 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
AIX Tick
CCSID 819 Tick
Take a look at the CCSID for the Queue manager that broker is using.
Then look into how to write a message with 1208 as the CCSID when the Broker uses AS_Q_DEF for the CCSID.
The WMQ PRogramming docs are the first place to start. Look at the options for MQPUT.
Then go back to Broker and apply the changes to the flow for do the same.
Oh, a little tip for the future.
Pleas put error output etc in CODE Tags and break the long lines of text up. IT really helps make the whole thing a bit more readable.
====
Edit
OR you could get the default CCSID of the QMGR changed to 1208 (UTF- .
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Tue Aug 17, 2010 11:34 pm Post subject: Re: Code page issue |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| smdavies99 wrote: |
Oh, a little tip for the future.
Please put error output etc in CODE Tags and break the long lines of text up. IT really helps make the whole thing a bit more readable. |
And a little tip for the present: to fix existing posts, look for the [Edit] button in the upper right corner. It makes it much easier for others to reply as well.
| kirank wrote: |
| Code: |
BIP2136E: Source character ''2026'' in field ''... 006f 2026 2026 002e ...'' cannot be converted from unicode to codepage '819'.
The source character is an invalid code point within the given codepage. |
I have copied the MQ headers from Input to output so the output has ccsid as 1208. |
Oh? Check again. Put a Trace node before 'EMM_SOSUBMIT_BAPI_SALESORDER.DestinationQueues' to display the message headers. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Aug 18, 2010 12:00 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
In my 'rather' limited experience with Broker, I have found that the safest way to change CCSID's in a Flow is NOT to copy the headers and change the MQMD.CodedCharSetId value.
Normally, I do something like this:-
| Code: |
after a Copy Headers
CREATE PROCEDURE DoStuff() BEGIN
SET OutputRoot.MQMD = NULL;
SET OutputRoot.MQRFH2 = NULL;
CREATE NEXTSIBLING of OutputRoot.Properties DOMAIN 'MQMD';
set OutputRoot.MQMD.Version = MQMD_CURRENT_VERSION;
SET OutputRoot.MQMD.CodedCharSetId = 923;
SET OutputRoot.MQMD.Format='MQSTR';
--
-- Now populate the OutputRoot.XMLNSC
|
The above example is for ISO-8859-15(923) but the principle will work for other CCSID's.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
