JMS Correlation ID not converting to EBCDIC Hexa

[Former Member]

We are using the PI 7.1 system on a AIX platform.

We use the JMS adapter to send messages to a MQ Queue manager on a AS400platform.

WebSphereMQ transport protocol is in JMS adapter.

We are generating custom dynamic correlation id using a UDF.

Expectation is to receive the correlation id in Ebcdic format because the

receiving end is a AS400 system.

But what I receive there is a Ascii Hexa.

For a example we are sending the correlation id as 0180000012. (ASCII)

What MQ receive is 30313830303030303132 (ASCII HEX)

Where what MQ should receive is F0F1F8F0F0F0F0F0F1F2 (EBCDIC HEX)

I need help to find out why JMS adapter is converting the correlation id

in to ASCII HEX without converting to EBCDIC HEX.

Appreciate a lot if any one can provide some help on this.

Thanks a lot,

Tania.

[stefan_grube]

I am not sure if I have understand the issue correctly.

Do you create an ASCII string and the ASCII characters are not converted into EBCDIC,

or do you create a HEX String?

Or does the JMS adapter converts your ASCII string to Hex?

I have the impression that the behaviour is a design gap, which nobody has noticed before.

A work around could be in converting the ASCII to EBCDIC inside the UDF,

Report this to SAP