This is very often a CCSID mismatch problem. Check the IBM side to see if the table is other than CCSID(65535) (no translate). Use locale
to check the language setting on the Informatica side. /opt/ibm/iSeriesAccess/bin/cwbnltbl
will describe the match between locale and CCSID. Assuming there's a mis-match:
To change or the add character set CCSID mapping, add the following lines to the $HOME/.iSeriesAccess/cwb_userprefs.ini
configuration file.
[CWB_CURRUSER\Software\IBM\Client Access Express\CurrentVersion\NLS] CCSID-CODESET=attr_str:939,IBM939,819,IBM819
The above example creates mappings for CCSID 939 to character set "IBM939" and for CCSID 819 to character set "IBM819".
Taken from ODBC language considerations