× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I've managed to copy the data in a readable form. Thought I would post in
case anyone else stumbles here while looking for a similar solution.
Thanks to Rob and Patrik, also an interesting analogy I read on jam and jam
jar labels that gave me a vital clue (just because it said CCSID 850 on the
label does not guarantee that it is CCSID 850)!

Conversion des CCSID

Cpy OBJ(&OBJ) TOOBJ(&StmF) DTAFMT(*TEXT) +

REPLACE(*YES) FROMCODPAG(1208) TOCODEPAGE(1252)



Copy to DDS file

CpyFrmImpF FromStmF(&StmF) ToFile(myFile)







date: Wed, 24 Mar 2021 17:18:42 +0100
from: Patrik Schindler <poc@xxxxxxxxxx>
subject: Re: Problem copying PC document to DDS file with accentuated
characters

Hello Dave,

Am 24.03.2021 um 15:30 schrieb Dave <dfx1@xxxxxxxxxxxxxx>:

I receive a CSV file from an external source by FTP

Which code page (charset) is this file supposed to have?

I upload it to QDLS (via the tool in ACS)


I don't know what ACS does in terms of charset translations, so I can't
help you here.

I copy it to my DDS PF with CPYFRMIMPF


Any options regarding charset you gave?

The CCSID is 850. The CCSID of my DDS PF is 297.

Sounds about right.

I can get round this by using SQL replace but surely there is a correct
way
to do this?

You can convert files in IFS with the CPY DTAFMT(*TEXT) command. See
online help text for it.

HTH.

:wq! PoC


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.