× 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.



So far, with the IFS API's all the letters are visually the same between the text file and the PF. I've dealt with French and Spanish characters before, and I can't recall ever having something that couldn't convert to 37.



-----Original Message-----
From: Jon Paris [mailto:jon.paris@xxxxxxxxxxxxxx]
Sent: Tuesday, February 13, 2018 5:54 PM
To: Midrange-L Midrange-l <midrange-l@xxxxxxxxxxxx>
Subject: Re: CPYFRMSTMF & character conversion

We were just trying to establish what you expected the mystery character to translate to?


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Feb 13, 2018, at 5:36 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

You are correct, there are other French characters as well.

I'm confused by your responses. I assume this is because I didn't state the problem clearly, so let me try again.

We have an existing process that takes a fixed-width text file in the QNTC file system and uses CPYFRMSTMF to import it into a flat PF. The problem that came up is with French characters in the text file. Flat PF's must have CCSID of 65535, which prevents CCSID conversion. Externally-described PF's can have other CCSID values, but they're incompatible with CPYFRMSTMF. CPYFRMIMPF requires a FLDDFNFILE when copying fixed-width data, and I don't have one.


I have a fix deployed, using the IFS API's. I'm willing to continue this discussion, or drop it. I will defer to you.

Thanks


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.