Guidelines for selecting a Rational ClearQuest data code page
Before you select a data code page, review the selection
guidelines to determine the appropriate data code page for a Rational®
ClearQuest® schema
repository.
These selection guidelines help determine the best code page for your Rational
ClearQuest environment.
- The data code page is supported by IBM® Rational ClearQuest and is tested and approved for use with it. These code pages are listed in Supported data code pages.
- The data code page is supported by the vendor databases that you use for all Rational ClearQuest databases within a single schema repository. You must set the vendor database character set of each user database to match the Rational ClearQuest data code page for its schema repository. For more information, see Vendor database character sets and the Rational ClearQuest data code page.
- All operating systems that run a Rational ClearQuest application must run one of the supported local character sets (locales).
- After you set the Rational ClearQuest data code page, users cannot enter characters that are not included in that data code page into the database records. However, characters that are excluded from the data code page can be entered in a file, such as a word-processing document, that is attached to the record.
- In some cases, a Rational ClearQuest data code page contains a subset of the characters in the corresponding vendor database character set. For example, in Japanese, the eucJP local character set contains the characters for half-width katakana. However, the corresponding data code page (60932) does not contain those characters. For a list of characters that are excluded from each Rational ClearQuest data code page, see Rational ClearQuest character exclusion lists.
- Rational ClearQuest validates data that is entered from integrations with other Rational products and with Microsoft Project. For more information, see Rational ClearQuest integrations and data code pages.
- If you are upgrading to version 8.0, it might be necessary to convert characters in an existing database to match the characters in your preferred data code page.