Use of DBCS characters in near term history situation names

Edit online

Exercise caution when you are working with history situation names that use a double-byte character set (DBCS).

Problem description

Situation names for near term history collections can be created and edited both on the enhanced 3270UI and the Tivoli Enterprise Portal Server. The portal server supports the use of double-byte character set (DBCS) characters, however, the enhanced 3270UI does not.

A DBCS supports national languages that contain many unique characters or symbols. Examples of such languages include Japanese, Korean, and Chinese.

Near term history situation names that are created with DBCS characters on a portal server appear garbled on the enhanced 3270UI. For example, the name displays control and other characters that do not make sense. You can edit the situation names on the enhanced 3270UI, however, do not attempt to do this as the original name is then corrupted on the portal server.

Symptoms of this problem are that historical collection situation names that use DBCS characters become corrupted on the Tivoli Enterprise Portal Server when they are edited with the enhanced 3270UI.

Solution

Use one of the following workarounds:
  1. Use only the Tivoli Enterprise Portal Server to change history collection names that use DBCS characters.
  2. Change the history collection name to one that does not use DBCS characters.