Conversion in HULFT10 for Container Services or HULFT10 for Container Platform

The conversion rules for Character (X) vary as follows, depending on the setting of X Type Conversion in the System Environment Settings:

When X Type Conversion is 'Mode 0'

HULFT carries out Code Conversion in the same manner as for Variable-length Characters (M).

HULFT converts the character codes in the transfer file on the host on the sending side, based on the code set that is registered in the Host Information.

When X Type Conversion is 'Mode 1'

HULFT converts control characters, including newline characters and shift codes, as single byte codes.

In file conversion between two of the Type-ASCII Code Sets, HULFT does not carry out conversion.

In conversion between the Type-ASCII Code Set and the Type-EBCDIC Code Set, HULFT converts character codes between EBCDIC and ASCII.

For EBCDIC, HULFT converts the codes based on the code sets that are specified for EBCDIC Set in the Send Management Information and in the Receive Management Information.

Note

  • Since the half-width Katakana characters in the EUC-JP code set are double byte codes, HULFT cannot convert them successfully if the following conditions are met:

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

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

  • Since the UTF-8 and GB18030 code sets contain multibyte characters, HULFT cannot convert them successfully if all the following conditions are met:

    • The transfer type is format transfer or multi format transfer

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

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