Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > Preparing for Implementation on the DB2 Host > Setting Up the Subsystem >

Choosing the Database CCSID


Siebel Systems supports both ASCII- and EBCDIC-based coded character set IDs (CCSIDs) on DB2 UDB for OS/390 and z/OS. The sort order used in list applets, among others, depends on the database CCSID.

Carefully read Release Notes for information about known restrictions; for example, the following features are not supported on Databases with EBCDIC code pages:

Development databases require ASCII code pages, because databases with EBCDIC code pages do not support two critical procedures in a development environment upgrade:

You can partition table spaces on a database with an EBCDIC code page, but you must modify the storage control file so that limit keys reflect the EBCDIC sort sequence. For more information, see Customizing a Development Environment.

You can deploy either an ASCII- or an EBCDIC-based CCSID to create your Siebel Schema, but it is generally recommended that you use ASCII.

CAUTION:  DB2 version 7 only supports a single code page for tables referenced within a single SQL statement.

Setting the CCSID

The CCSIDs must be configured in the fields ASCII CODED CHAR SET or EBCDIC CODED CHAR SET on the DB2 installation panel DSNTIPF. The field DEF ENCODING SCHEME on the same panel determines whether the default encoding scheme is ASCII or EBCDIC.

NOTE:  The field MIXED DATA on DSNTIPF should equal NO for all supported languages except Japanese.


 Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS 
 Published: 18 April 2003