Working with HCL Compass data code pages

After you determine the appropriate HCL Compass data code page and create a vendor database instance with the corresponding vendor database character set, you can perform the tasks outlined in this topic.

  • Create a Compass schema repository by using the Maintenance Tool.
  • If the database contains only ASCII data, change the data code page for an existing schema repository by using the Maintenance Tool.
  • Specify file encoding when exporting user and group information by using the User Administration Tool.
  • Select the file encoding when exporting the results of a query by using the Export Tool.
  • Select the file encoding when exporting a profile by using the Maintenance Tool.
  • Create a new user database, selecting from all schemas defined in the schema repository.
    • Newly created schema repositories with data code page values of 932 or 60932 (Japanese), or 936 (Simplified Chinese) contain matching localized and ASCII versions of every schema included with the product.
    • Newly created schema repositories with data code page 65001 (UTF-8) contain all localized versions, ASCII, Japanese, and Chinese.
    • Other code page schema repositories contain only ASCII schema versions.

    Localized schema version names reflect their language and the package version numbers.

  • Install or upgrade packages in a schema by selecting from a list of the latest available packages compatible with the Compass data code page of the schema repository. The Package and Package Upgrade wizards display the latest matching localized versions:
    • 932 or 60932 (Japanese): ASCII or Japanese packages
    • 936 (Simplified Chinese): ASCII or Chinese packages
    • 65001 (UTF-8): ASCII, Japanese, or Chinese packages
    • In all other schema repositories, the wizards display only ASCII package versions.

Compass continues to provide two command line utilities, codepageutil and installutil, which you can use to move data between existing database sets, while ensuring that the characters in your existing database sets are supported by your target data code page.