UTF-16 implementation details

Accounting Integrator uses the UTF-16 plane 0 in where each character is stored on 2 bytes. In this storage mode, you:

  • Can encode on a single byte a great number of unrecognized characters
  • Cannot encode graphical characters that are defined on 4 bytes.

AI Enabler characteristics

Before you can process your UTF-16 data in the Rule Engine, you must set the configuration parameters of your UTF-16 Server in the AI Enabler.

You define the encoding attributes in the Folder description and enter the configuration parameters in the Finance objects. You can enter UTF-16 data in the arguments of user tables as well as in the associated values.

As soon as your configuration is validated, it is deployed on the Rule Engine(s) in disconnected mode.

For more information on parameter settings and compatibility rules, refer to the AI Enabler online documentation.

Restrictions

You are not allowed to:

  • Enter UTF-16 characters in objects identifiers. They can only contain ASCII characters.
  • Use UTF-16 characters to create a mapping expression. You can, however, enter your UTF-16 expression in the Initial value of a Variable then use this Variable in your mapping expression (the maximum number of objects for this type is increased to 5000).
  • Use packed data in UTF-16 Folders.
  • Enter more than 110 characters (220 bytes) in the argument of a user table entry.

Rule Engine

In the Rule Engine, the following files are in UTF-16 format:

  • Configuration files forwarded to the Rule Engine (ctx.mvt and mvt.mvt files).
  • Session input files, including the script. fic file.
  • Restriction: In MVS, the rdjenv file remains in EBCDIC format; in Windows or UNIX, environmment variables are in ASCII format.
  • Component files (Output-Events, anomalies, reports)

Exits and external calls have been adapted to process UTF-16 data.

Restrictions

You can only use TABLEL table files.

The Turbo version is not available in this mode.

Related Links