CCSID conversion considerations for DB2 Universal Database for z/OS and DB2 Universal Database server for VM database managers

One of the differences between a DB2 Universal Database™ for iSeries™ and other DB2^® databases is that the iSeries system supports a larger set of CCSIDs. This can lead to errors when the other database managers attempt to perform character conversion on the data (SQLCODE –332 and SQLSTATE 57017).

Certain fields in the DB2 UDB SQL catalog tables might be defined to have a DBCS-open data type. This is a data type that allows both double-byte character set (DBCS) and single-byte character set (SBCS) characters. The CCSID for these field types is based on the default CCSID shipped with the server.

When these fields are selected from a DB2 Universal Database for z/OS^® or DB2 Universal Database Server for VM application requester (AR), the SELECT statement might fail because the DB2 Universal Database for z/OS and DB2 Universal Database Server for VM databases might not support the conversion to this CCSID.

To avoid this error, you must change the DB2 Universal Database for z/OS database or the DB2 Universal Database Server for VM AR to run with either one of the following items:

The same mixed-byte CCSID as the DBCS-OPEN fields in the iSeries SQL catalog tables.
A CCSID that the server allows conversion of data to when the data is from the mixed-byte CCSID of the DBCS-OPEN fields in the iSeries SQL catalog tables. This CCSID might be a single-byte CCSID if the data in the iSeries SQL catalog tables DBCS-OPEN fields is all single-byte data.

This requires some analysis of the CCSID conversions supported on the DB2 Universal Database for z/OS or DB2 Universal Database Server for VM so you can make the correct changes to your server. See the DB2 UDB for z/OS Administration Guide for specific information on how to handle this error.