Hi Werner,
Now, cURL is supporting only IBM-1047 and ISO8859-1 encodings for existent tagged files.
And all new files created by cURL is being saved as ASCII and tagged as ISO8859-1 (the trace files are included).
In next build, there is a planning to add the following environment variables:
_ENCODE_FILE_NEW
- to set encoding and tag for the new files.
It’s allow to choose output encoding for files.
_ENCODE_FILE_EXISTING
- to control reading/writing untagged files properly.
They could be set to the following values: ISO8859-1, IBM-1047, UNTAGGED, BINARY.
Unfortunately, if you have files in another encoding (for example, IBM-1141) you need to convert them to ISO8859-1 or IBM-1047 and tag them in according with their encoding before using by cURL.
iconv -f IBM-1141 -t IBM-1047 file1 > file2
chtag -tc IBM-1047 file2
or
iconv -f IBM-1141 -t ISO8859-1 file1 > file2
chtag -tc ISO8859-1 file2
I’m studying your case and will discuss with team is there a possibility to use another EBCDIC code pages.
Thanks,
Sergey