DTLUCBRG disregards the CODEPAGE statement in the DBMOVER configuration file and instead uses the code page that is used to store registrations and capture data map metadata, as follows:
IBM037 on i5/OS
IBM1047 on z/OS
UTF-8 on Linux, UNIX, or Windows
Whenever the DBMOVER CODEPAGE statement is overridden, PowerExchange issues the following message:
Changed client code pages to
name
(
internal_code_page_number
)
On i5/OS and z/OS, PowerExchange supports table and column names with characters that are present in code pages IBM037 and IBM1047, respectively. Accented characters that are not in the code pages are not supported. On Linux, UNIX, and Windows, all characters are supported.
When the PowerExchange Listener retrieves data, code page conversion of SQL and data is performed automatically. For example, a PowerExchange Listener on z/OS might need to use a particular SQL code page to meet the requirements of a DB2 subsystem. SQL is converted to the required code page and is received by the Listener ready for use by DB2. Column data is described according to the DB2 CCSIDs and sent back to DTLUCBRG, which converts it to the required metadata code page.