Points to note for UTF-8

Conversion of Double-byte Graphic Characters (N) type

For points to be noted when the field type in the Format Information is Double-byte Graphic Characters (N), refer to the following:

• Conversion from UTF-8 and GB18030

• Space code conversion rules

Conversion of Character (X) type

When the Code Set for Transfer on the host on the sending side is UTF-8, HULFT cannot carry out Code Conversion properly if both of the following conditions are met:

• 'Mode 1' is specified for X Type Conversion in the System Environment Settings

• Character (X) is specified for the field type in the format information

In this case, HULFT handles and processes data as single byte codes.

Codes that cannot be used as the first character

You cannot use custom characters starting with '0x00,' because UTF-8 supports only variable-length characters.

EBCDIC User Table

When the Code Set for Transfer of the host on the sending side or the host on the receiving side is UTF-8, you cannot use an EBCDIC user table.

System Environment Settings

When the Code Set for Transfer of the host on the sending side or the host on the receiving side is UTF-8, the behavior of HULFT may vary depending on the configuration of the settings related to Code Conversion in the System Environment Settings.

Code Conversion Mode

When the Code Set for Transfer of the host on the sending side or the host on the receiving side is UTF-8, the behavior of HULFT is the same as when Code Conversion Mode is '1.'

Standard for Japanese

In the case of UTF-8, '83JIS' is the fixed setting of Standard for Japanese (jistype) (JIS Year)

For details on the settings of the System Environment Settings, refer to the following:

Conversion of UTF-8 host-type-dependent characters

In Japanese character code conversion, the conversion results of some codes in UTF-8 vary depending on the host type.

For details, refer to Conversion of UTF-8 host-type-dependent characters.