Upgrading encodings to MB or 6.2 and later versions

This only applies to situations where a user-configured encoding transformation (using hcitpstblconvert or msgmapdata) is used in an earlier Cloverleaf version. That is, any encoding performed in Tcl using hcitpstblconvert, msgmapdata or any other method, including the standard ones provided. This does not apply for any other use.

Users with SNA interfaces communicating to EBCDIC (Extended Binary Coded Decimal Interchange Code) systems must be aware of this.

Two options are available for upgrading non-standard encodings to multi-byte or CIS:

  • Option 1: Use the existing hcitpstblconvert.

    Select the binary encoding option from the Network Configurator.

    If the IB message data is not a standard encoding supported by the IBM ICU library and is being translated by a user Tcl proc, then the IB encoding binary should be selected for the IB protocol thread. By selecting binary encoding, you can continue to use the user-configured encoding transformation table of the earlier version.

    Note: The binary option must be used if the ICU library does not support encodings found in the current and previous Cloverleaf versions of Tcl. IBM037 is a common standard encoding.
  • Option 2: Remove the existing hcitpstblconvert.

    Add the correct encoding to the .ini file so that it displays on the Network Configurator’s Encoding menu. Then, you can configure the thread to use the newly added encoding.

For example, IBM037 is not on the encoding list, so it must be added. To do this:

  1. Navigate to server/i18n.ini.
  2. Add IBM037 after ASCII. It is then available on the Encoding menu.