Bookshelf Home | Contents | Index | PDF |
Implementing Siebel Business Applications on DB2 UDB for z/OS > Preparing for Implementation on the DB2 Host > Setting Up the DB2 Subsystem > Considerations in Choosing the Database CCSIDSiebel Systems supports both ASCII- and EBCDIC-based coded character set IDs (CCSIDs) on DB2 for z/OS. The database CCSID you use determines a number of factors, for example, the sort order used in list applets. Review the Release Notes on Siebel SupportWeb for information about known restrictions; for example, the following features are not supported on databases with EBCDIC code pages: You should run development databases with ASCII code pages, because databases with EBCDIC code pages do not support the following procedures in a development environment upgrade:
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.
You can partition table spaces on a database with either an ASCII or an EBCDIC code page, so that limit keys reflect the sort sequence difference between ASCII and EBCDIC. For more information, see Configuring the Database Layout. NOTE: DB2 for z/OS v7 only supports a single code page for tables referenced within a single SQL statement. Setting the CCSIDConfigure the CCSIDs on the DB2 installation panel, DSNTIPF, in the fields ASCII CODED CHAR SET or EBCDIC CODED CHAR SET. The field DEF ENCODING SCHEME on the same panel determines whether or not the default encoding scheme is ASCII or EBCDIC. NOTE: Set the value of the MIXED DATA field on the DSNTIPF panel to NO for all supported languages except Japanese. |
Implementing Siebel Business Applications on DB2 UDB for z/OS |