The documentation portal is undergoing maintenance. During this period, you can't create any new user credentials. If you do, you'll need to recreate the user credential after the maintenance period ends.
The USE_TYPE1_FALLBACKS statement enables type 1 fallback mappings for all code pages. A type 1 fallback mapping is a one-way mapping from a Unicode character to a character in the output code page.
To enable type 1 fallback mappings, PowerExchange calls the ucnv_setFallback() API for all code pages that it uses.
All
ICUCNVPROPERTY
No
USE_TYPE1_FALLBACKS={
N
|Y}
N
.
Type 1 fallback mappings are not globally enabled.
Y.
Type 1 fallback mappings are enabled for all code pages.
Default is N.
When PowerExchange converts data between Unicode and a source or target code page, type 1 fallback mappings are disabled by default. That is, when the code page conversion routine encounters a character mapping with a precision indicator of 1 in the UCM file, the mapping is not executed. Instead, the conversion routine generates a substitution output character.
To enable type 1 fallback mappings, define USE_TYPE1_FALLBACKS=Y in the DBMOVER configuration file. Alternatively, you can enable type 1 fallback mappings for a specific code page by using the USE_TYPE1_FALLBACKS option of the ICUCNVPROPERTY statement in the DBMOVER file.
In a PowerExchange session, a code page conversion routine might use type 1 fallback mappings when writing data to a target. Type 1 fallback mappings are not typically used when reading data from a PowerExchange source.
Informatica recommends that you enable type 1 fallback mappings whenever you use PowerExchange to write multibyte data to a target.