I'm anxious to follow this thread as we've received UNICODE text files and
placed them directly onto the IFS. CPYFRMSTMF was then used to move to
physical file and we've experienced the same "extra" space between every
Our solution was to open in NOTEPAD and save as "ANSI". That output text
file was then usable with the above...
Not an automated or sustainable solution, but one that I recall having to
work around after trying various combinations of CCSID with no success.
On Tue, Apr 9, 2013 at 5:37 PM, Gary Thompson <gthompson@xxxxxxxxxxx> wrote:
My first attempt at "consuming" a .txt file in, I think, Unicode format
did not work as expected.
CPYFRMIMPF did copy the data to the local EBCDIC file, but the data
was still "double byte" (an "extra" space between each character).
I tried both
CCSID is described as UTF-16 BE and it seems to be a Windows "standard"
for text files.
Thanks for any advice . . .
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives