Hi Nick,
Please take care not to mix up the two MQMD fields related to data conversion. One is called CCSID and one is called Encoding.
The CCSID field, Coded Character Set ID to give it its full name, is where the code page value goes.
The Encoding field is where the numeric encoding goes, including reflecting things like Big Endian and Little Endian numeric arrangements.
An Encoding of decimal value 785, is a hexadecimal value of 0x00000311, which is the default, and very standard, and expected z/OS encoding.
Can you expand a little on what made you believe that the encoding was invalid? You haven't shown us enough of the Dead Letter message data for us to be able to determine the reason for the message being placed on the Dead-Letter queue - that data is scrolled off the right hand side of your "Message data bytes" window.
I can see from the left hand side of your "Message data bytes" window that the CCSID of the original message was indeed 875 as your question suggests you want it to be.
Cheers,
Morag
------------------------------
Morag Hughson
MQ Technical Education Specialist
MQGem Software Limited
Website:
https://www.mqgem.com------------------------------
Original Message:
Sent: Fri January 20, 2023 12:29 PM
From: NICK DAKORONIAS
Subject: MQ INVALID MSG ENCODING 785
Hello MQ community users,
We have received a msg at DEAD LETTER QUEUE hosted at z/OS v2.3 MQ with invalid encoding 785., as depicted below.
FYI, z/OS QM has CCSID 875 (EBCDIC GREEK).
Can you pls advise whether 785 is mistype - java app code (GPP -> Global Pay Plus) instead of the valid CCSID 875?
As far as I Know, there is no CCSID such as 785 available globally.

Any advise on the above will be much appreicated.
Cheers, Nick
------------------------------
NICK DAKORONIAS
Application Integration & Middleware Solution Certified Specialist
Kyndryl
Athens
------------------------------