topic Re: Unicoding problem in Application Development and Automation Discussions

Unicoding problem

Former Member — Tue, 18 May 2010 08:09:28 GMT

i had a requirement.

Data delivered by mainframe host are read and processed by the above report.

Inputfile could not be read caused by incorrect character encoding.

Data are stored in EBCDIC on the mainframe host and cannot be delivered using UTF-8, only as ISO8859 15 (Latin 9).

following report needs to be changed:

ZDE_ITELLIUM_EINGANG

These reports read files from the application server or write to it as well as using GUI_UPLOAD or GUI_DOWNLOAD.

In each case an encoding option has to be used.

In this context we need SAP-encoding 1164 which is ISO8859-15 (Latin-9).

Please use SPACE as replacement character in case of conversion errors.

We recommend to add a new Parameter for the encoding on the selection-screen.

what needs to be done in the above case

Re: Unicoding problem

Former Member — Tue, 18 May 2010 08:14:58 GMT

You have been given all the information required, even the exact codepage is given, what problem are you facing in using this codepage?

Re: Unicoding problem

Former Member — Tue, 18 May 2010 09:02:54 GMT

OPEN DATASET p_file FOR INPUT IN TEXT MODE ENCODING DEFAULT. ( deleted )

OPEN DATASET p_file FOR INPUT IN TEXT MODE ENCODING DEFAULT IGNORING CONVERSION ERRORS. ( added )

GUI_UPLOAD / GUI_DOWNLOAD

CODEPAGE should be '1164' instead of SPACE.

Please reply ASAP.

Thanks

Re: Unicoding problem

Former Member — Tue, 18 May 2010 09:08:07 GMT

You have a code page parameter in GUI_UPLOAD and GUI_DOWNLOAD. Mention the codepage 1164 in that. Even in OPEN DATASET statement you have the code page addition in that. Hit F1 on OPEN DATASET and check the syntax

Re: Unicoding problem

Former Member — Wed, 19 May 2010 11:10:13 GMT

Hi!

Try this go to se80 put your program name and enter goto attributes check/uncked 'Unicode checks active'