Additional '0D''0A' being placed at end of message data.

[Former Member]

I have a file on the SAP file system. This file has mulitple lines in it and the lines are seperated with '0A' (New Line Character).

I read the file using a file adapter and add a 200 character header to the begining of the first line.

When we write the data using the JMS Adapter (Websphere) all the data gets put on the queue correctly including the header with this exception. Appended to the last line in the data are '0D' '0A'. How do I stop this from happening?

[stefan_grube]

I know that there was a bug with this effect.

If you do not have the latest SP level, install it.

Regards

Stefan

[Former Member]

You are correct I do mean '0x0D' and '0x0A'

[Former Member]

are you sure you don't mean something like this for a new line?

'0x0D''0x0A'

[Former Member]

You are correct

[Former Member]

OK so are you saying that '0x0D''0x0A' is being appended to the end of the line or that you had it typed wrong in your adapter and that is why it wasn't working? if '0x0D''0x0A' doesn't work then go with 'nl' instead.

'nl' works with windows and '0x0D''0x0A' is good for unix systems

Edited by: Alex on Jul 21, 2008 6:02 PM

[Former Member]

No that is not what I'm saying. I don't have the '0x0A' '0x0D' configured at all.

Each line of the input file ends with a '0x0A'....

example:

abc'0x0A'

def'0x0A'

It is picked up and sent to the JMS Adapter.

When I look at the message on the queue it looks like this:

example:

abc'0x0A'

def'0x0A''0x0D''0x0A'