Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

You told curl that it is utf-8?
When you use MQ Explorer. Does the message look correct in hexadecimal format?

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

You told curl that it is utf-8?
When you use MQ Explorer. Does the message look correct in hexadecimal format?

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

You told curl that it is utf-8?
When you use MQ Explorer. Does the message look correct in hexadecimal format?

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

You told curl that it is utf-8?
When you use MQ Explorer. Does the message look correct in hexadecimal format?

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

Hi Dan. Posting a message with Hebrew chars into the cloud qmgr works.
-H "Content-Type: text/plain;charset=utf-8" --data @hebrew.utf8
I will check if MQ Explorer displays it correctly.

You told curl that it is utf-8?
When you use MQ Explorer. Does the message look correct in hexadecimal format?

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

In field message data MQ explorer displays it correctly.
The byte stream in message data byte looks correct, too.
Just the right hand side looks literally questionable.

Hi Dan. Posting a message with Hebrew chars into the cloud qmgr works.
-H "Content-Type: text/plain;charset=utf-8" --data @hebrew.utf8
I will check if MQ Explorer displays it correctly.

You told curl that it is utf-8?
When you use MQ Explorer. Does the message look correct in hexadecimal format?

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

In field message data MQ explorer displays it correctly.
The byte stream in message data byte looks correct, too.
Just the right hand side looks literally questionable.

Hi Dan. Posting a message with Hebrew chars into the cloud qmgr works.
-H "Content-Type: text/plain;charset=utf-8" --data @hebrew.utf8
I will check if MQ Explorer displays it correctly.

You told curl that it is utf-8?
When you use MQ Explorer. Does the message look correct in hexadecimal format?

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

-H "Content-Type: application/json;charset=utf-8" --data @hebrew.json

No idea. The long list of fixes indicates a long list of bugs. Some of which are still unknown.
Are any other tools in your environment having issues when exchanging data between z/os and windows. E.g. when you send a utf8 file from Windows to z/os and back. Is it still utf8 or something else.
Or when you put a utf8 message in z/os into the queue. Is MQ explorer then able to display it correctly?

In field message data MQ explorer displays it correctly.
The byte stream in message data byte looks correct, too.
Just the right hand side looks literally questionable.

Hi Dan. Posting a message with Hebrew chars into the cloud qmgr works.
-H "Content-Type: text/plain;charset=utf-8" --data @hebrew.utf8
I will check if MQ Explorer displays it correctly.

You told curl that it is utf-8?
When you use MQ Explorer. Does the message look correct in hexadecimal format?

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

-H "Content-Type: application/json;charset=utf-8" --data @hebrew.json

No idea. The long list of fixes indicates a long list of bugs. Some of which are still unknown.
Are any other tools in your environment having issues when exchanging data between z/os and windows. E.g. when you send a utf8 file from Windows to z/os and back. Is it still utf8 or something else.
Or when you put a utf8 message in z/os into the queue. Is MQ explorer then able to display it correctly?

In field message data MQ explorer displays it correctly.
The byte stream in message data byte looks correct, too.
Just the right hand side looks literally questionable.

Hi Dan. Posting a message with Hebrew chars into the cloud qmgr works.
-H "Content-Type: text/plain;charset=utf-8" --data @hebrew.utf8
I will check if MQ Explorer displays it correctly.

You told curl that it is utf-8?
When you use MQ Explorer. Does the message look correct in hexadecimal format?

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

-H "Content-Type: application/json;charset=utf-8" --data @hebrew.json

No idea. The long list of fixes indicates a long list of bugs. Some of which are still unknown.
Are any other tools in your environment having issues when exchanging data between z/os and windows. E.g. when you send a utf8 file from Windows to z/os and back. Is it still utf8 or something else.
Or when you put a utf8 message in z/os into the queue. Is MQ explorer then able to display it correctly?

In field message data MQ explorer displays it correctly.
The byte stream in message data byte looks correct, too.
Just the right hand side looks literally questionable.

Hi Dan. Posting a message with Hebrew chars into the cloud qmgr works.
-H "Content-Type: text/plain;charset=utf-8" --data @hebrew.utf8
I will check if MQ Explorer displays it correctly.

You told curl that it is utf-8?
When you use MQ Explorer. Does the message look correct in hexadecimal format?

I just googled "Hebrew characters in UTF-8" and the first hit was this:

https://www.utf8-chartable.de/unicode-utf8-table.pl?start=1280

search for the word "hebrew" on this page.

Can you say a little more about how you are providing your JSON message to the REST interface? Is it a file? Is the file in UTF-8?

Cheers,
Morag

Hi Dan. Your non english characters should work with UTF-8.

UTF-8 is not a charset. It is a character encoding system that works well with Arabic, Russian and other non English language characters. Each unicode character can be encoded in UTF-8.

Still it were nice if IBM also supported UTF-16 as encoding system.

Was this ever solved?

I have used the sample dotnet vb SimplePut example to write to a queue; and then using MQ 9.3.3 REST API for messaging; and it fails as

{    "error": [        {            "msgId": "MQWB0309E",            "action": "Resubmit the request, correcting any issues.",            "completionCode": 0,            "reasonCode": 0,            "type": "rest",            "message": "MQWB0309E: The received or browsed message type is unsupported by the mqweb server.",            "explanation": "The mqweb server successfully received an MQ message, but was of an unsupported message type."        }    ]}

and when using `amqsbcgc` the output is

AMQSBCG0 - starts here********************** MQOPEN - 'TEST.QUEUE.1' MQGET of message number 1, CompCode:0 Reason:0****Message descriptor****  StrucId  : 'MD  '  Version : 2  Report   : 0  MsgType : 8  Expiry   : -1  Feedback : 0  Encoding : 546  CodedCharSetId : 1200  Format : '        '  Priority : 0  Persistence : 0  MsgId : X'414D5120415050543032202020202020C55AC26401C47AA7'  CorrelId : X'000000000000000000000000000000000000000000000000'  BackoutCount : 0  ReplyToQ       : '                                                '  ReplyToQMgr    : 'QM1                                          '  ** Identity Context  UserIdentifier : 'user1     '  AccountingToken :   X'160105150000007E46FCF3D997C6E2B1A0FF3F97DD000000000000000000000B'  ApplIdentityData : '                                '  ** Origin Context  PutApplType    : '11'  PutApplName    : 'ePut\bin\Debug\SimplePut.exe'  PutDate  : '20230919'    PutTime  : '04395225'  ApplOriginData : '    '  GroupId : X'000000000000000000000000000000000000000000000000'  MsgSeqNumber   : '1'  Offset         : '0'  MsgFlags       : '0'  OriginalLength : '-1'****   Message      **** length - 24 of 24 bytes00000000:  7400 6500 7300 7400 2000 6D00 6500 7300           't.e.s.t. .m.e.s.'00000010:  7300 6100 6700 6500                               's.a.g.e.        ' No more messages MQCLOSE MQDISC

Hi Om,

You appear to be suffering from a different problem. This thread is about string messages in different codepages. Your message is a binary message not a string message.

I expect when you put the message with the SimplePut.exe executable you probably intended it to be a string message, but its format is blank (which means binary) and the REST API only supports string messages. Perhaps you can correct the SimplePut.exe executable to fill in the MQMD Format field correctly, or use another application to put your test message that already puts MQSTR as the value in the MQMD Format field. amqsput is one such example application.

Then try retrieving that message with the REST API.

Cheers,
Morag

Was this ever solved?

I have used the sample dotnet vb SimplePut example to write to a queue; and then using MQ 9.3.3 REST API for messaging; and it fails as

{    "error": [        {            "msgId": "MQWB0309E",            "action": "Resubmit the request, correcting any issues.",            "completionCode": 0,            "reasonCode": 0,            "type": "rest",            "message": "MQWB0309E: The received or browsed message type is unsupported by the mqweb server.",            "explanation": "The mqweb server successfully received an MQ message, but was of an unsupported message type."        }    ]}

and when using `amqsbcgc` the output is

AMQSBCG0 - starts here********************** MQOPEN - 'TEST.QUEUE.1' MQGET of message number 1, CompCode:0 Reason:0****Message descriptor****  StrucId  : 'MD  '  Version : 2  Report   : 0  MsgType : 8  Expiry   : -1  Feedback : 0  Encoding : 546  CodedCharSetId : 1200  Format : '        '  Priority : 0  Persistence : 0  MsgId : X'414D5120415050543032202020202020C55AC26401C47AA7'  CorrelId : X'000000000000000000000000000000000000000000000000'  BackoutCount : 0  ReplyToQ       : '                                                '  ReplyToQMgr    : 'QM1                                          '  ** Identity Context  UserIdentifier : 'user1     '  AccountingToken :   X'160105150000007E46FCF3D997C6E2B1A0FF3F97DD000000000000000000000B'  ApplIdentityData : '                                '  ** Origin Context  PutApplType    : '11'  PutApplName    : 'ePut\bin\Debug\SimplePut.exe'  PutDate  : '20230919'    PutTime  : '04395225'  ApplOriginData : '    '  GroupId : X'000000000000000000000000000000000000000000000000'  MsgSeqNumber   : '1'  Offset         : '0'  MsgFlags       : '0'  OriginalLength : '-1'****   Message      **** length - 24 of 24 bytes00000000:  7400 6500 7300 7400 2000 6D00 6500 7300           't.e.s.t. .m.e.s.'00000010:  7300 6100 6700 6500                               's.a.g.e.        ' No more messages MQCLOSE MQDISC