On 09 Apr 2013 16:51, Joe Wood wrote:

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

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.


Given the command of interest is CPYFRMSTMF vs CPYFRMIMPF, that would probably justify a new thread. The features for the two commands are significantly different for their intent. Anyhow...

Was the STMFCCSID parameter used in a particular combination that did not give the expected results, perhaps using CCSID(1200) CVTDTA(*AUTO), to denote that the data in the STMF is UNICODE UTF-16BE? If the CCSID tagging for the STMF is established properly, then the CCSID(*STMF) CVTDTA(*AUTO) should probably work. The feature assumes an EBCDIC CCSID for the database file as target of the copy when the DBF is assigned *HEX to indicate /no translation/ should occur; i.e. conversion is effected regardless, using the "default job CCSID". FWiW the STMFCODPAG should probably no longer be used, and is mutually exclusive to a specification of a STMFCCSID.

_i Copy From Stream File (CPYFRMSTMF) i_
"The Copy From Stream File (CPYFRMSTMF) command copies the data in a stream file to either a database file member or a save file.

_Data conversion options (CVTDTA)_

Specifies the process for converting the data from the stream file to the database file member.

This parameter is ignored when copying to a save file.


The data is converted during the copy operation using the coded character set identifier (CCSID) of the stream file and the database file CCSID.


_Stream file CCSID (STMFCCSID)_

Specifies the method of obtaining the stream file coded character set identifier (CCSID) used for data conversion.

This parameter is ignored when copying to a save file, or when CVTDTA(*TBL) or CVTDTA(*NONE) is specified.

This parameter can not be specified with the Stream file code page (STMFCODPAG) parameter.


The CCSID associated with the stream file specified on the From stream file (FROMSTMF) parameter is used for data conversion.


Use the CCSID associated with the stream file specified on the From stream file (FROMSTMF) parameter to compute a CCSID in the Microsoft Windows encoding scheme (x4105). This CCSID is used if data conversion is requested. This option allows data to be converted properly if the data was created using Microsoft Windows. ("Microsoft" and "Windows" are registered trademarks of Microsoft Corporation)

For example, if the CCSID associated with the stream file is 37, the stream file data is instead assumed to be in CCSID 1252 for data conversion.

Specify the stream file CCSID to be used for data conversion.


This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page