DB2/400 databases use a specific term "CCSID" to describe the encoding used for the data stored in the database. CCSID can be defined in DB2/400 for each column separately.
It is worth noting that during the reverse of DB2/400, CCSIDs are not automatically reversed. Therefore, all intermediary tables will be created with the default CCSID of the database.
In most cases this won’t cause any problems, but sometimes it might lead to conversion problems like this:
java.sql.SQLException: [SQL0332] Character conversion between CCSID 1200 and CCSID 65535 invalid.
In this situation, reversing the CCSID may fix the issue.
In case you ever experience any problems related to CCSID, it is worth trying to use the attribute "Reverse CCSID" to get the CCSIDs into your Metadata.
This information will be then used by Semarchy xDM Data Integration druing the creation of the intermediary tables and may ultimately solve your problem.
To use the attribute: . Open DB2/400 Metadata and click on the schema. . In the "Advanced" tab, enable the attribute "Reverse CCSID" . Then reverse your Metadata once again and save it:
You can consult the reversed CCSIDs in the "Advanced" tab when you click on the specific column that has a defined CCSID in your database.