If you import a remote COBOL file that contains DBCS or non-ASCII
data, the import operation might seem to succeed although the data is corrupted.
Problem
When the following conditions apply, the imported
data is corrupted although the operation seems to be successfully completed:
- You use the Import COBOL Files wizard to import a remote COBOL file or
copybook that contains non-ASCII characters in a COBOL VALUE clause.
- You use the Remote Systems Explorer to set up the remote connection.
- You set the local encoding setting for the connection to UTF-8.
Solution
Download the file to your workstation
and import the file locally.