You can use dynamic character mapping to dynamically update the static encoding maps used by the multi-byte or double-byte encodings in the ePortal encoding library. This allows you to add site-specific character mappings.
To update the dynamic character map, edit the text file CharacterMappings.txt. This file is located in the root of an MCP COBOL data source project, OS 2200 Open DTP data source project, or OS 2200 TIP data source project.
The following is an example of a CharacterMappings.txt file:
OVERWRITE_ALLOWED: FALSE
BEGIN_MAPPING: LETSJ
2121:ADE4
2160:ADB5
2161:ADB6
2162:ADB7
2163:ADB8
2164:ADB9
END_MAPPING:
BEGIN_MAPPING: LETSJKANJI
2121:ADE4
2160:ADB5
2161:ADB6
2162:ADB7
2163:ADB8
2164:ADB9
END_MAPPING:
In the preceding example, the BEGIN_MAPPING keyword marks the beginning of the character mapping values, and also contains the name of the character encoding to which the mapping is applied. The END_MAPPING keyword marks the end of a mapping. Multiple character mappings can be defined in the character mapping file.
The OVERWRITE_ALLOWED keyword is used to indicate if the character mappings are allowed to overwrite existing static character mappings defined for a character encoding.
The following are the rules for creating a character mapping file:
Comments start with a # character. Any text after the comment character is ignored.
The character mapping files must be encoded as UTF-8.
Mappings have the format <aaaa>:<nnnn>, where <aaaa> is a UTF-16 character value, and <nnnn> is the encoded character value. Both are expressed as hexadecimal values.
Each mapping must be on a separate line.
When mapping a single-byte character, 0x00 is placed in the upper byte.