Use general code pages if the default code pages that PowerExchange supplies are not sufficient for your installation. PowerExchange uses general code pages to transmit data or metadata between systems.
Typically, general codes pages are used in the following circumstances:
Multibyte data is processed.
Data is outside of the ISO-8859 range on Linux, UNIX, or Windows, or outside of the IBM-037 range on i5/OS or z/OS.
Enter general code pages in the CODEPAGE statement of the DBMOVER configuration file. You can define the following types of general code pages in the CODEPAGE parameter:
The following table describes the uses of each code page type that can be specified in the CODEPAGE parameter:
Names of databases, tables columns, or files.
User IDs or passwords.
Column and parameter data used on nonrelational database types where the code pages have not been specified, for example, at the field or data map level.
Parameter data refers to data sent to the server and substituted where parameter markers (question marks) are present in Delete, Select, or Update SQL.
Code page of SQL used to access data.
Typically, the SQL code page is the same as the control code page because table names can be processed by both.
The SQL code page must be sufficiently precise to handle any literals.
If you specify the control code page and omit the data control and SQL code pages, PowerExchange uses the control code page for the data control and SQL code pages. For example, the following statements are equivalent:
If you omit the CODEPAGE parameter on Linux, UNIX, or Windows, PowerExchange uses the following default values:
If you omit the CODEPAGE parameter on i5/OS or z/OS, PowerExchange uses the following default values:
The PowerExchange Navigator overrides the code page specified in the DBMOVER configuration file, so that it can handle all characters. The PowerExchange Navigator uses UTF8 for the control, data, and SQL code pages.