ASNA BTerm Admin Manual

Double Byte Support

This topic describes BTerm's support for languages which use the Double Byte Character Set (DBCS).

New Support in 14.0

As of version 14.0, the following DBCS code pages will be supported with the optional ASNA DBCS library. This library is a drop-in that can be recognized by the ASNA runtime via the Microsoft Extensibility Framework (MEF). Support for other CCSIDs can be added by the user via MEF by implementing the ASNA.Runtime.IConverterFactory interface. Converters added via MEF will take precedence over existing converters (e.g. if you use the ASNA DBCS library the converter for 37 will be taken from it instead of using the default provided by .Net – 37 is included in the DBCS library as it’s needed by 937).

For reference, the CCSIDs defined on the IBM i are listed here.

CCSID Description
37USA, Canada (S/370), Netherlands, Portugal, Brazil, Australia, New Zealand
290Japan Katakana (extended)
833Korea (extended)
834Korea - including 1880 UDC
835Traditional Chinese - including 6204 UDC
836Simplified Chinese (extended)
837Simplified Chinese - including 1880 UDC
939Japan English/Kanji (extended) - including 4370 UDC
1364Korea (extended)
1388Traditional Chinese
1399wJapan English/Kanji
4396Japan - including 1880 UDC
4930Korea Windows
5026Japan Katakana/Kanji (extended) - including 1880 UDC
5035Japan English/Kanji (extended) - including 1880 UDC
5123Japanese Latin Host Extended SBCS (includes euro)
13124Traditional Chinese
16684Japanese Latin Host Double-Byte including 4370 UDC (includes euro)

The DBCS is the IBM i's support for languages requiring more than 256 characters. In it, each character is represented by 2 bytes (hence Double-Byte).

The DBCS supports four languages:

  • Simplified Chinese
  • Traditional Chinese
  • Japanese
  • Korean

There are multiple CCSIDs that can be used for each of the above languages; these have been introduced and updated over time to include additional characters like the Euro. IBM i and BTerm both support Unicode as a special case (support for Unicode and Double-Byte was added with BTerm 8.0).

A great deal of information on the topic can be found in at http://www-03.ibm.com/systems/i.software/globalization/codepages.html in PDF form. It covers the current IBM code pages, many of which are supported by IBM i servers.

DBCS Types

There are 4 "types" of DBCS fields in DDS. For more detail on the types, check here: (http://pic.dhe.ibm.com/infocenter/iseries/v6r1m0/index.jsp?topic=/rzakc/dbcdtype.htm):

  • J (Only) – accepts only DBCS characters. The Field Length must be an even number (of bytes). The display station automatically inserts shift-control characters in fields specified with this data type.
  • E (Either) – accepts either DBCS or alphanumeric (single byte) characters. The field length must be an even number (of bytes)
    DBCS or alphanumeric characters can be typed into the field. The type of data entered into the field's first position determines the type of data that the rest of the field will accept. If blank, the system assumes alphanumeric data will be entered Positioning the cursor on the field and putting the keyboard in DBCS mode readies the field to accept DBCS data.
  • O (Open) – accepts a mixture of single- and double-byte characters. The length must be a multiple of 1 (bytes).
    If the field contains DBCS data, the system does not ensure that the data is enclosed between shift-control characters.
  • G (Graphic) — accepts exclusively DBCS data. The length specifies the number of characters, not of bytes.
    Data typed in this field does not contain shift-control characters.

A unicode field is considered type "G" with a explicit CSID value of 1200 for UTF-16 and 13488 for UCS-2.

For more information on Unicode fields in IBM i, check here http://pic.dhe.ibm.com/infocenter/iseries/v6r1m0/topic/rzakc/dspfil.htm

In BTerm the special case for Unicode has been promoted as a separate DBCS type.