DBCS field mapping considerations

 

The table shows what types of data mapping are valid between physical and logical files for double-byte character set (DBCS) fields.

Physical file data type	Logical file data type
	Character	Hexa- decimal	DBCS- open	DBCS-either	DBCS- only	DBCS-graphic	UCS2- graphic	UTF-8	UTF-16
Character	Valid	Valid	Valid	Not valid	Not valid	Not valid	Valid	Valid	Valid
Hexadecimal	Valid	Valid	Valid	Not valid	Not valid	Not valid	Not valid	Not valid	Not valid
DBCS-open	Not valid	Valid	Valid	Not valid	Not valid	Not valid	Valid	Valid	Valid
DBCS-either	Not valid	Valid	Valid	Valid	Not valid	Not valid	Not valid1	Not valid1	Not valid1
DBCS-only	Valid	Valid	Valid	Valid	Valid	Valid	Not valid1	Not valid1	Not valid1
DBCS-graphic	Not valid	Not valid	Valid	Valid	Valid	Valid	Valid	Valid	Valid
UCS2-graphic	Valid	Not valid	Valid	Not valid1	Not valid1	Valid	Valid	Valid	Valid
UTF-8	Valid	Not valid	Valid	Not valid1	Not valid1	Valid	Valid	Valid	Valid
UTF-16	Valid	Not valid	Valid	Not valid1	Not valid1	Valid	Valid	Valid	Valid
In the table, 1 indicates that these mappings are not supported because of the possibility of substitution characters appearing after conversion.

 

Parent topic:

Double-byte character set considerations